Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.



You can use this Snap to both read the input document data and write the data in the binary (parquetParquet) format to the output.


Snap Type




Number of Views

Examples of Upstream and Downstream Snaps





  • Min: 1

  • Max: 2

  • Mapper

  • Copy

Requires document data as input.

You can override the schema setting by inserting an object like this into the second input view.




  • Min: 1

  • Max: 1

  • Parquet Writer

  • Parquet Parser

Writes the document data in the binary (parquetPprquet) format to the output.


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 when running the Pipeline pipeline by choosing one of the following options from the When errors occur list under the Views tab:

  • Stop Pipeline Execution: Stops the current Pipeline pipeline execution if the Snap encounters an error.

  • Discard Error Data and Continue: Ignores the error, discards that record, and continues with the remaining records.

  • Route Error Data to Error View: Routes the error data to an error view without stopping the Snap execution.

Learn more about Error handling in Pipelines.


Field Name

Field Type




Default ValueParquet Formatter
ExampleTransform Parquet Formatter


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.


Edit Schema









Specify a valid Parquet schema that describes the data.  

The following is an example of a schema using all the primitive and some examples of logical types:

Code Block
message document {
  # Primitive Types
  optional int64 32_num;
  optional int64 64_num;
  optional boolean truth;
  optional binary message;
  optional float pi;
  optional double e;
  optional int96 96_num;
  optional fixed_len_byte_array (1) one_byte;
  # Logical Types
  optional binary snowman (UTF8);
  optional int32 8_num (INT_8);
  optional int32 16_num (INT_16);
  optional int32 u8_num (UINT_8);
  optional int32 u16_num (UINT_16);
  optional int32 u32_num (UINT_32);
  optional int64 u64_num (UINT_64);
  optional int32 dec_num (DECIMAL(5,2));
  optional int32 jan7 (DATE);
  optional int32 noon (TIME_MILLIS);
  optional int64 jan7_epoch (TIMESTAMP_MILLIS);
  optional binary embedded (JSON);

"Generate template" does not support nested structures like MAP and LIST type.






Default Value: NONE

Example: SNAPPY

Dropdown list

Choose the type of compression to use when writing the file. The following are the available options:

  • NONE


  • GZIP

Many compression algorithms require both Java and system libraries, and the algorithms fail if the latter is not installed. If you see unexpected errors, ask your system administrator to verify if all the required system libraries are installed ; because they are typically not installed by default. The system libraries have names such as or and could can be located in the /usr/lib/x86_64-linux-gnu directory.


Decimal rounding mode


Default Value: Half up

Example: Up

Dowpdown Dropdown list

Select the required rounding method for decimal values when they exceed the required number of decimal places. The following are the available options:

  • Half up

  • Half down

  • Half even

  • Up

  • Down

  • Ceiling

  • Floor

  • Truncate

Snap execution

Default ValueValidate & Execute
Example: Execute only

Dropdown list

Select one of the following three modes in which the Snap executes:

  • Validate & Execute: Performs limited execution of the Snap, and generates a data preview during Pipeline pipeline validation. Subsequently, performs full execution of the Snap (unlimited records) during Pipeline pipeline runtime.

  • Execute only: Performs full execution of the Snap during Pipeline pipeline execution without generating preview data.

  • Disabled: Disables the Snap and all Snaps that are downstream from it.


Code Block
   "schema": "message document {\n  optional binary AUTOSYNC_PRIMARYKEY (STRING);\n  optional binary AUTOSYNC_VALUEHASH (STRING);\n  optional binary AUTOSYNC_CURRENTRECORDFLAG (STRING);\n  optional int64 AUTOSYNC_EFFECTIVEBEGINTIME (TIMESTAMP(MILLIS,true));\n  optional int64 AUTOSYNC_EFFECTIVEENDTIME (TIMESTAMP(MILLIS,true));\n  optional double ID1;\n  optional binary ID2 (STRING);\n  optional binary ID3 (STRING);\n  optional binary ID4 (STRING);\n  optional binary ID5 (STRING);\n  optional binary ID6 (STRING);\n  optional binary ID7 (STRING);\n  optional binary ID8;\n  optional double ID9;\n  optional double ID10;\n  optional double ID11;\n  optional double ID12;\n  optional double ID13;\n  optional double ID14;\n  optional int32 ID15 (DATE);\n  optional int64 ID16 (TIMESTAMP(MILLIS,true));\n  optional int64 ID17 (TIMESTAMP(MILLIS,true));\n  optional int64 ID18 (TIMESTAMP(MILLIS,true));\n  optional double ID100;\n}\n"




Document Data into Parquet Format and Vice Versa

This example demonstrates how to convert the input document data to parquet and parquet data back to document output.


Step 3: Configure the Parquet Parser Snap, on . On validation, the Snap reverts the Parquet data to document data.


  1. Download and import the Pipeline pipeline into the SnapLogic Platform..

  2. Configure Snap accounts, as applicable.

  3. Provide Pipeline parameters, as applicable.