In this article
Table of Contents | ||||
---|---|---|---|---|
|
Overview
You can use this read type Snap to read binary data from various sources such as SLDB, HTTP, S3, SFTP, HDFS, and produces a binary data stream at the output. Unlike the File Reader Snap, this Snap can read more than one file in the given directory and its subdirectories recursively.
Prerequisites
Multiexcerpt include macro | ||||
---|---|---|---|---|
|
Support for Ultra Pipelines
Works in Ultra Pipelines.
Limitations
- For most file protocols, the Snap behaves the same way in both Snaplex and Groundplex. However, the HDFS protocol works only in a Groundplex. The Hadoop cluster must open to the Groundplex server instance without any authentication.
Known Issues
None.
Snap Input and Output
Input/Output | Type of View | Number of Views | Examples of Upstream and Downstream Snaps | Description |
---|---|---|---|---|
Input | Document |
| N/A | N/A |
Output | Binary |
|
| Binary data read from the source specified in the Selected files property. |
Account
This Snap uses account references created on the Accounts page of SnapLogic Manager to handle access to this endpoint. This Snap supports a Basic auth account, an AWS S3 auth account, SSH Auth account, SMB account, or no account. See Configuring Binary Accounts for information on setting up accounts that work with this Snap. Account types supported by each protocol are as follows:
Protocol | Account types |
---|---|
sldb | no account |
s3 | AWS S3 |
ftp | Basic Auth |
sftp | Basic Auth, SSH Auth |
ftps | Basic Auth |
hdfs | no account |
http | no account |
https | no account |
smb | SMB |
wasb | Azure Storage |
wasbs | Azure Storage |
gs | Google Storage |
Note |
---|
The FTPS file protocol works only in explicit mode. The implicit mode is not supported. |
Required settings for account types are as follows:
Account type | Settings |
---|---|
Basic Auth | Username, Password |
AWS S3 | Access-key ID, Secret key |
SSH Auth | Username, Private key, Key Passphrase |
SMB | Domain, Username, Password |
Azure Storage | Account name, Primary access key |
Google Storage | Approval prompt, Application scope, Auto-refresh token (Read-only properties are Access token, Refresh token, Access token expiration, OAuth2 Endpoint, OAuth2 token and Access type.) |
Snap Settings
Field Name | Field Type | Description | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Label* | 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. Default Value: Multi File Reader | |||||||||||||||
Selected Files | Use this field set to define data sources. This field set contains Folder/File, Wildcard, and Include subfolders fields. Click to add a data source. Add each entry in a separate row.
| ||||||||||||||||
Folder/File | String/Expression | Specify the URL for the data source, which can be a directory or a file. It should begin with a file protocol. The supported file protocols are:
The File property should have the syntax:
Default Value: [None] Example:
| |||||||||||||||
Wildcard | String/Expression | Specify the wildcard pattern, if the URL in the Folder/File property is for a directory. All files matching the wildcard pattern are selected. This property is not supported for the sldb, http, and https protocols. The asterisk pattern character ("*", also called "star") and the question mark ("?") are supported. The "*" character matches zero or more characters. The "?" matches exactly one character.
| |||||||||||||||
Include Subfolders | Checkbox | Select to search subfolders for the specified Wildcard if Folder/File is set to a directory. If you select this checkbox and the Folder/File property is a folder, all files in the subfolders matching the given wildcard pattern are selected. | |||||||||||||||
Number of retries | Integer | Specify the maximum number of retry attempts the Snap must make in case there is a network failure, and the Snap is unable to read the target file. If the value is larger than 0, the Snap first downloads the target file to a temporary local file. If any error occurs during the download, the Snap waits for the time specified in the Retry interval and attempts to download the file again from the beginning. When the download is successful, the Snap starts to stream the data from the temporary file to the downstream pipeline. All temporary local files are deleted when they are no longer needed.
Minimum value: 0 Default Value: 0
| |||||||||||||||
Retry interval (seconds) | Integer | Specify the minimum number of seconds for which the Snap must wait before attempting recovery from a network failure. Minimum value: 1 Default value: 1 | |||||||||||||||
|
| ||||||||||||||||
Snap Execution | Dropdown list |
|
Note |
---|
The Pipeline validation (achieved by pressing "Retry") imposes a 5-minute timeout. If there are a large number of files to be read by the Snap as a result of Wildcard and Include subfolders settings, the Snap validation may fail due to this 5-minute timeout limit. |
Output Fields for the Different Protocols
The output fields that the Multi File Reader Snap generates depends on the protocol you select. The following table lists the output fields for the different protocols supported by the Snap:
Protocol | Output Fields |
---|---|
S3 |
|
SLDB |
|
|
|
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|