In this article
Overview
You can use this Snap to read data from upstream Snaps and prepare them for writing into Adobe Enterprise Platform (AEP) as JSON or Parquet files.
Prerequisites
The schema that you want to use with this Snap should exist in the Adobe Experience Platform. If you do not have the schema ready, create it using the Adobe Experience Platform user interface before using this Snap.
Limitations and Known Issues
While the Schema Name, Dataset Name, and Connectors Object Name fields are expression enabled, their purpose is to read Pipeline parameter values. This Snap does not read values from upstream Snaps. You can, however, add this Snap in Pipelines with other Snaps to execute them in a sequence.
Snap Input and Output
Input/Output | Type of View | Number of Views | Compatible Upstream and Downstream Snaps | Description |
|---|---|---|---|---|
Input | Document |
|
| Each input document contains documents that must be prepared for writing to Adobe Experience Platform. |
Output | Document |
|
| Each output document lists out the absolute path to the reformatted output file. |
Snap Settings
Parameter Name | Data Type | Description | Default Value | Example |
|---|---|---|---|---|
Label | String | Required. The name for the Snap. Modify this to be more specific, especially if there is more than one of the same Snap in the Pipeline. | Adobe Experience Platform File Generator | Read and Reformat Documents from S3 |
Schema Name | String | Required. The name of the schema to be used to create the output Parquet or JSON file. This schema should already have been created in AEP. This Snap reads Pipeline parameters, but not values from upstream Snaps. You can, however, add this Snap in Pipelines with other Snaps to execute them in a sequence.
| N/A | Snaplogic Demo Experience Event Schema |
Schema Type | String | Required. The schema type that you want to use to create the output file. Click to select from the following options:
| Parquet | JSON |
Snap Execution | String | Select one of the three modes in which the Snap executes. Available options are:
| Execute only | Validate and Execute |
Troubleshooting
Error | Reason | Resolution |
|---|---|---|
Invalid Snap configuration | Property Schema Name is null or missing. This typically means that either you did not specify the schema that you want to use or misspelled the schema name. | Provide a valid schema name. |
Unable to load the private key for the given alias | Keystore file not found at the given keystore path. | This error appears when the account doesn't have valid values. Ensure that the keystore path, keystore passphrase, private key alias, and private key passphrase are correct. Also, you must upload the keystore in the Keystore Path that you specify. |
Unable to obtain access token | This message appears when the endpoint account details are incorrect. | Check your Organization ID, Technical Account ID, Client ID, Client Secret Key details and try again. |