Versions Compared

Version Old Version 77 New Version 78
Changes made by

Lakshmi Manda

Lakshmi Manda

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel1
outlinefalse
typeflat
printablefalse

...

Snap Pack

Date

Snap Pack Version

Updates

Teradata

439patches29265

  • Fixed an issue with the Teradata FastLoad Snap that incorrectly validated successfully even when the fast load was paused due to an error. The Snap now displays the error with the appropriate reason for the pause.

  • Fixed an issue with the Teradata FastLoad Snap that generated where an invalid output document even was generated when an error occurred whenwhile fetching the table schema with , and the Create table if not present, checkbox , is deselected. Now, regardless of the checkbox status, the Snap correctly displays an error if an error occurs when fetching the table schemain such cases, regardless of the checkbox status.

Salesforce

439patches29230

Fixed the vulnerabilities in CXF library dependencies within the Salesforce Snap Pack to enhance security and ensure reliable functionality.

OpenAI LLM

439patches29164

Azure OpenAI LLM

439patches29063

Enhanced the following accounts in the Snap Pack with the Read timeout (seconds) field that enables the Snap to wait for a response from Azure:

SAP

439patches29181

Enhanced the SAP Execute Snap with the Round to SAP decimal checkbox that enables the Snap to round the decimal value to match the number of Decimal Places defined in the SAP target field. This property only applies to the SAP packed decimal fields, which store data in the BCD (Binary Coded Decimal) format.

JDBC

439patches29008

  • Upgraded the JOOQ library of the JDBC Snap Pack from v3.9.1 to v3.17.x. Pipelines using the Generic - JDBC Snaps might be impacted by the jOOQ upgrade because the latest jOOQ version is not fully backward-compatible. Learn more.

  • Fixed an issue with Generic JDBC - Execute and Select Snaps when connecting to the Oracle database where the data was displayed in an unexpected structure and without the actual row address value when querying table columns of ROWID type. Now, the Snaps handle the ROWID type columns correctly to prevent the display of the nested output when ROWID is combined in the query with other selected columns.

Note

Breaking change:

With the 439patches29008 Snap Pack version, if any of your existing pipelines with the Generic JDBC Execute and Select Snaps when connecting to the Oracle endpoint use the encoded ROWID (by manually handling the Base64 encoded data), your pipelines might break. To prevent your pipelines from failing, you must update your Snap Pack version to the previous version.

Behavior change:

Earlier, the ROWID columns were displayed in binary (Base64 encoded data) form in the output. With the 439patches29008, the Generic JDBC Execute and Select Snaps that integrate with the Oracle endpoint display the ROWID columns in string form in the output (which can be used for other operations downstream).

API Suite

439patches29124

  • Fixed an issue in the GraphQL Client Snap where improper extensions caused a validation error; however, it resulted in an empty error view when the Route Error Data to Error View was enabled.

  • Fixed an issue with the GraphQL Client Snap that did not load the Query Builder properly.

Transform

439patches29078

Fixed an issue with the CSV Parser Snap that introduced unexpected characters into the records and output data because of incorrect handling of the delimiter.

Salesforce

439patches29014

Fixed an issue with the Salesforce Lookup, SOQL, and SOSL Snaps, where errors were not routed to the error pipeline when Route Error Data to Error View was enabled, and a referenced expression variable was missing in the upstream or pipeline parameters.

Oracle

439patches29008

Fixed an issue with Oracle Execute, Select, and Stored Procedure Snaps where the data was displayed in an unexpected structure and without the actual row address value when querying table columns of ROWID type. Now, the Snaps handle the ROWID type columns correctly to prevent the display of the nested output when ROWID is combined in the query with other selected columns.

Note

Breaking change:

With the 439patches29008Snap Pack version if any of your existing Oracle pipelines use the encoded ROWID(by manually handling the Base64 encoded data), your pipelines might break. To prevent your pipelines from failing, you must update your Snap Pack version to the latest version.

Behavior change:

Earlier, the ROWID columns were displayed in binary (Base64 encoded data) form in the output. With the 439patches29008, the Oracle Execute and Select Snaps display the ROWID columns in string form in the output (which can be used for other operations downstream).

AutoSync

Nov 19, 2024

439patches29077

438patches29076

Fixed an issue loading to Databricks. To consume this fix:

  • For a version 4.39 AutoSync Snaplex or Groundplex, upgrade data pipelines with Databricks as a target to use the AutoSync 439patches29077 Snap Pack.

  • For a version 4.38 AutoSync Snaplex or Groundplex, upgrade data pipelines with Databricks as a target to use the AutoSync 438patches29076 Snap Pack.

...

Important Updates from Snowflake

Deprecated Drivers:

As of February 1, 2024, Snowflake has ceased support of older driver versions in compliance with its Support Policy. You must upgrade to the latest driver version to access important security, performance, and functionality improvements. Ensure that your Snowflake pipelines use the Snowflake JDBC Driver v3.13.27 or a higher version. Learn how to check your current driver version. The Snowflake Snap Pack is bundled with the 3.16.0 JDBC driver, but if you are using your own version, it may be deprecated in accordance with Snowflake Guidelines.

Security Policies:

Snowflake recently signed the Cybersecurity and Infrastructure Security Agency (CISA) Secure By Design Pledge. In line with CISA’s Secure By Design principles, Snowflake recently announced several security enhancements in their platform — most notably the general availability of Trust Center and a new Multi-Factor Authentication (MFA) policy.

Effective October 2024, MFA will be enforced by default for all human users in any new Snowflake account. Service users (accounts designed for service-to-service communication) will not be subject to this MFA requirement.

Basic Authentication Accounts:

If you currently use Basic authentication to access Snowflake, we recommend one of the following:

  • Update your password to a maximum of 14 characters and a minimum of 8, and ensure it does not match any of the previous five passwords. Learn more.

  • Migrate to Key-Pair authentication: This method involves generating a public and private key pair, where the private key is securely stored and the public key is registered with your Snowflake account.

  • Migrate to OAuth2 authentication: This is a widely adopted standard for secure delegated access. It allows applications to obtain limited access to user accounts on an HTTP service, facilitating safer and more manageable authentication flows.

Implementing the above recommendations will secure your data and protect sensitive data, ensuring compliance with Snowflake's updated security policies. Learn more. For questions, contact support@snaplogic.com.

Breaking Changes

Note

JDBC Snap Pack:

Reltio Account deprecation by the end of October 2024

  • Reltio has announced the deprecation of basic authentication using username and password for API access by the end of October 2024 to enhance their platform security. All customers must adopt client credentials and stop using username/password for API access immediately. Reltio will disallow API access using username/password by the end of October 2024. Client credentials are required for any integration or API usage with Reltio.

  • Consequently, SnapLogic deprecated the Reltio Account in the October 2024 release. Any existing Reltio pipelines that rely on the current Reltio Account that uses a username/password for API access will not be supported by Reltio. To ensure the continuity of your pipelines, we recommend that you use the Reltio OAuth2 Account.

...