...
Snap type:
...
Format
...
Description:
...
This Snap serializes incoming SnapLogic document objects into Avro-formatted data.
- Expected upstream Snaps: A Mapper Snap must be used in front of this Snap to map the fields present in .avsc schema file.
- Expected downstream Snaps: Any binary output processing Snap can be used downstream.
- Expected input: The input for this Snap must be created through the upstream Mapper Snap.
- Expected output: The output of this Snap should be a serialized binary stream that contains data and its schema.
...
[None]
...
Accounts are not used with this Snap.
...
This Snap has exactly one document input view.
...
In this article
| Table of Contents | ||||
|---|---|---|---|---|
|
Overview
You can use this Snap to serialize the incoming SnapLogic document objects into Avro-formatted data.
...
Snap Type
Avro Formatter Snap is a FORMAT-type Snap that formats data to Avro-formatted data.
Prerequisites
None.
Support for Ultra Pipelines
Does not support Ultra Pipelines.
Limitations and Known Issues
None.
Snap Views
Type | Format | Number of Views | Examples of Upstream and Downstream Snaps | Description |
|---|---|---|---|---|
Input | Document |
|
| This Snap exposes the avsc schema in its input view. You must use |
...
a Mapper Snap in front of this Snap to map the fields present in |
...
. |
...
avsc schema file. |
Output |
...
Settings
Label
...
Document |
|
| Any serialized binary stream output processing Snap that contains data and its schema. | |
Error | Error handling is a generic way to handle errors without losing data or failing the Snap execution. You can handle the errors that the Snap might encounter while running the Pipeline by choosing one of the following options from the When errors occur list under the Views tab. The available options are:
Learn more about Error handling in Pipelines. | |||
Snap Settings
| Info |
|---|
|
Field Name | Type | Description |
|---|---|---|
Label* Default Value: Avro Formatter | String | Specify the name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your |
...
Pipeline. |
Schema |
...
File* Default Value: [None] | String/Expression | Specify the path to the schema file in .avsc format |
Ignore empty stream Default value |
|---|
...
| Multiexcerpt include macro | ||||
|---|---|---|---|---|
|
...
| Multiexcerpt include macro | ||||
|---|---|---|---|---|
|
...
: Deselected | Checkbox | Select the checkbox to specify an action that the Snap must take if the input view contains empty documents. If selected, the Snap does not write anything to the output if no documents are received in the input. Else, the Snap writes an empty array in the output view if no documents are received in the input view. |
|---|
Default value: Not selected
Snap Execution Default value: Validate & Execute | Dropdown list | Select one of the three modes in which the Snap executes. Available options are:
|
|---|
Examples
Transforming CSV data to Avro format
This example pipeline demonstrates how to convert CSV data to Avro format as per the specified schema and transform it to generate reports or update a database. The output is the transformed and formatted data ready for further processing.
...
Configure the File Reader Snap to read the leads.csv file. On validation, the Snap displays the data in binary format.
 |  |
2. Configure the CSV Parser Snap to parse the binary input of the leads.csv file. On validation, the Snap displays the structured data.
 |  |
3. Configure the Avro Formatter Snap to convert the CSV data to Avro format as per the defined Schema file. On validation, the Snap displays the Avro-formatted data.
 |  |
4. Configure the Avro Parser Snap to parse the Avro-formatted data. On validation, the Snap displays the deserialized data.
 |
|
5. Configure the Mapper Snap to extract the data. On validation, the Snap displays the output based on the specified mappings.
 |
|
Downloads
| Attachments | ||||
|---|---|---|---|---|
|