August 2024

main27765

21 Aug 2024 

Stable

Upgraded the org.json.json library from v20090211 to v20240303, which is fully backward compatible.

Enhanced the Decompress Snap to support encrypted and unencrypted ZIP and 7z files through the new File Password Account type.

The Azure Data Lake Account has been removed from the Binary Snap Pack because Microsoft retired the Azure Data Lake Storage Gen1 protocol on February 29, 2024. We recommend replacing your existing Azure Data Lake Account with other Azure Accounts.

Fixed an SMB (server message block) connectivity issue within the Binary Snap Pack, as the incorrect name provided by the SMB client did not match the Windows cluster virtual name, affecting the SPN (service principal name) connection.

Fixed a null pointer exception in the Public Key Account for Binary Snap Pack when the Public Key field value is null. Now, the account displays a configuration exception for a null value.

Fixed an issue with the File Writer Snap, which partially writes the file for some FTPS servers by pausing for seconds before closing the output stream as specified in the global property ftpsDelayBeforeClosing.

Fixed an issue with the Binary Snaps that failed to build a data connection when connecting to the FTP server over FTPS protocol.

Updated and certified against the current SnapLogic Platform release.

Fixed an issue that occurred when node properties were used to override default algorithm specifications for SFTP operations.

Fixed an issue that caused NTLM authentication issues when trying to access SMB servers.

The JSON key field in the Binary Google Service Account supports JSON strings. You can upload the JSON key either from SLDB or dynamically pass the value using a pipeline parameter or access values from Secrets Manager.

August 2023

main22460

Stable

Updated and certified against the current SnapLogic Platform release.

• Fixed an issue with the PGP Sign Snap that caused an error when using an encryption subkey for signing.
• Fixed an issue with the File Writer Snap where the file was unable to validate when the File action field was set to IGNORE for the WASB and WASBs protocols.

433patches21913

• Dynamic ports are supported for the SMB file protocol.
• Fixed an issue with the File Writer Snap that caused slow performance when writing large files and the Flush interval was set to a positive value.

433patches21645

With the 4.33 GA release, support for some algorithms for SFTP connection negotiation is removed for improved security and because we’ve updated the library used to connect to SFTP sources. With Snap Pack version 433patches21645, you can modify the global properties. Refer to the Configuration Settings for Snaps documentation for details about how to revert to the previous settings.

Fixed the issues with the AES Encrypt and AES Decrypt Snaps, where the Snaps previously did not include the error stack trace in the error view. The Snaps now provide detailed information in case of any issues or errors.

• Fixed an issue with the File Delete Snap where the Snap failed with a 404 Not Found error when trying to delete files from an Amazon S3 bucket. This issue occurred only with the Identity and Access Management (IAM) role in an Amazon AWS S3 Account.

• Fixed an issue where Binary Snaps could not handle region information for the Amazon S3 file protocol, which resulted in an error.

The Key passphrase field in the Private Key Account now supports expressions, allowing dynamic evaluation using pipeline parameters when the expression button is enabled.

432patches20458

Fixed an issue where the ZipFile Read and ZipFIle Write Snaps failed to display the input schema for the File or File name field when using an expression.

• Fixed an issue where the File Writer Snap would not retry on completing the writing of the file.

• Added a configuration warning message when using the WASBS protocol with AzCopy, as it supports only the HTTPS protocol.

The JSCH library has been upgraded to version 0.2.7.

The PGP Decrypt Snap now allows you to skip the signature verification when you face an issue with the signature in the encrypted file.

• The File Delete Snap now passes the input document to the error view correctly.

• The AWS S3 and S3 Dynamic accounts now support the maximum session duration of an IAM role defined in AWS.

430patches17292

• The File Operation Snap supports moving data from a local node to an Azure blob through the AZ Copy utility.

• The Azure Storage Account includes the Request Size (MB) field to set the buffer limit before writing to Azure storage to enhance the performance.

• The SSH Auth Account supports dynamic values for the following fields that allow you to use Pipeline parameters.

  • Username

  • Private key

  • Key passphrase

429patches16569

Enhanced the following Snaps and Accounts that use SnapLogic File System (SLFS) to display Lint warnings in Pipelines when using incorrect file paths to read and write files. We recommend that you use the File Upload :Upload_icon: icon to specify the file path.

• File Writer

• File Reader

• File Delete

• HDFS Reader

• HDFS Writer

• HDFS ZipFile Reader

• HDFS ZipFile Writer

• S3 File Writer

• S3 File Reader

• ORC Reader

• ORC Write

• ZipFile Read

• ZipFile Write

• Google Service Account

• Two-Factor Auth Account

• Fixed an issue with the Directory Browser Snap where the Snap failed while parsing the value in the Amazon S3 client region.
• Enhanced the File Writer Snap with the Prevent URL encoding checkbox to manage the URL encoding. Select this checkbox to prevent the encoding of the file path URL automatically. This allows the Snap to use the file path value as-is. Deselect this checkbox to automatically encode the characters in the File URL.
• Fixed an issue with the ZipFile Write Snap where the Snap displayed a null pointer exception when the path in the upstream File Reader Snap started with "../".
• Fixed an issue in the File Reader Snap where the Snap displayed an SMB Mount error when trying to connect to Mount Share. This Snap now supports SMB version 3.1.1.
• Fixed an issue with the File Writer Snap where the Snap did not display an error when an error occurred while writing a file.

428patches14736

Fixed an issue in the File Writer, S3 File Writer, and ZipFile Write Snaps where the Snaps failed with AccessControlListNotSupported error when using an external AWS account to write to the bucket if it has the bucket-owner-enforced setting enabled. With this fix, you can select the None option (the default value), from the AWS Canned ACL dropdown list, indicating that no Canned ACL request is set when writing a new file to prevent the error.

• Enhanced the File Operation Snap to support Azure Data Lake Storage (ADLS) Gen2 protocol for moving and copying files in the Azure Blob File System (ABFS).

• Fixed an issue with the File Poller Snap to enhance performance of the polling operations that allows the Snap to poll the files without stopping.

• Enhanced the File Writer, S3 File Writer, and ZipFile Write Snaps with the AWS Canned ACL (Access Control List) permission mode that enables you to use Canned ACLs when creating the S3 Object. This feature allows you to grant full access of the object to the S3 bucket owner.

• Fixed an issue with the File Writer Snap where the Server Message Block (SMB) mount failed to connect unless the Pipeline was restarted.

• Enhanced the S3 File Writer Snap with the Suggest fully-qualified file names checkbox that allows you to use fully-qualified file names in the File name Suggestions list for gov cloud instances.

• Fixed an issue with the File Poller Snap to handle indefinite polling operations without stopping in the process of execution.

• Fixed an issue with the ZipFile Write Snap where the ZIP extension files were downloaded with an incorrect file extension.

• Fixed an issue with the Zip File Read Snap where an archive failed to uncompress.

• Fixed an issue with the File Writer Snap when a file greater than 10 MB failed to write when uploading to Google Storage.

• Upgraded the Google Cloud Storage Java libraries from version 1.105.1 to version 2.2.2.

427patches13004

Fixed an issue with the SMB Account where the Snaps could not re-establish a lost connection to the SMB mount point.

• Enhanced the File Operation Snap with a new field Azcopy absolute path that enables the Snap to make a single API call to move an entire directory. This field supports directory and wildcard characters for Azure blob storage for all three operations: Copy, Move and Rename.
• Enhanced the Azure Storage Account with a new option called SAS URI in the Auth Type dropdown. This enables you to select either Access Key or the SAS URI while configuring the account settings.

Fixed a memory leak issue when using HDFS protocol in Binary Snaps.

• Fixed an issue with the Decompress Snap, where the Snap prematurely uncompressed multi-stream BZIP2 files.
• Enhanced the PGP Encrypt Snap with improved memory usage and also fixed an issue with this Snap, where the Snap failed to encrypt large size files due to the lack of memory.

425patches10994

• Removed duplicate strings in the request’s User Agent header sent by  S3 File Writer and S3 File Reader Snaps to display the string without any duplicates.
• Enhanced the Directory Browser Snap to process the files with the owner field for the SFTP protocol. Upon validation, the output of the Snap fetches the owner’s name, which was previously displayed as unknown.
• Fixed an issue with the File Writer Snap where the Snap fails to connect to the SFTP endpoint using the AWS Transfer Family.
• Fixed an issue where integration Pipelines fail to connect the SFTP Server with the Binary Snap Pack when upgraded to the SnapLogic 4.25 release version (main9554).

• Fixed the following issues in the PGP Decrypt Snap caused due to the Snap patch 425patches9581:
  • The Snap writes an empty document to the output view when there is an error in the Snap. It will now decrypt the document and write it to the output view only if it succeeds.
  • The Snap fails to decrypt any non-signed encrypted file more than 500 bytes. It will now decrypt both non-signed and signed encrypted files. 
  • Removed the Project ID field from the Google Service Account, since the JSON Key already contains information about the Project ID. 

Enhanced the SFTP session in Binary Snaps to support the SFTP servers which close SFTP sessions slowly.

Enhanced the S3 File Writer to use an MD5 checksum that automatically checks for data integrity and corruption while uploading the file.  

Fixed the file operation error of copying large S3 files in the File Operation Snap by supporting the transfer of zero-byte S3 files while uploading a file.

• Fixed the missing library error in Binary Snap Pack when running Hadoop Pipelines in JDK11 runtime.
• Enhanced the Binary Snap Pack by adding a new account Two-Factor Auth Account that supports two layers of authentication for Secure File Transfer Protocol (SFTP). The two secure layers of verification to grant access include the Basic Auth (username/password) and the SSH Key (username/private key) methods.

Fixed an issue in the File Writer Snap with the ADL protocol, to perform the correct action when OVERWRITE is selected from the File Action drop-down field.

Fixed an encryption issue with the File Operation Snap by implementing both SSE-KMS and SSE-S3 supports to the Snap.

Fixed an issue in the Snap Pack by removing the plaintext credentials in file URL from JCC log messages.

Enhanced the Snap Pack by upgrading SMB client library.

Fixed an issue with the File Writer Snap by avoiding overwriting of documents when using appending the data to a CSV file in SFTP.

Rolled back the recent patch to Binary Snap Pack (File Writer Snap - 423patches7923) that might have induced SSL handshake failures/terminations in existing Pipelines. 

Fixed an issue with File Writer Snap by skipping the validation of the SAS URI having write permission, if the SAS URI uses an access policy.

Enhanced the File Poller Snap by adding a field, Exit on first matches, which when set to true stops the Snap from executing after the first file paths matching the filter are written to the output view. If the field is not configured or is set to false (default value), then the Snap continues to poll the directory until the Polling timeout is reached.