Versions Compared

Key

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

...

Upgrading to this Release

...

...

Dot Releases: Snaps

Snap Pack

Date

Snap Pack Version

Updates

Teradata

439patches29265

  • Fixed an issue with the Teradata FastLoad Snap that 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 where an invalid output document was generated when an error occurred while fetching the table schema, and the Create table if not present, checkbox is deselected. Now, the Snap correctly displays an error in 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, existing pipelines using the Generic JDBC Execute and Select Snaps may experience issues when connecting to the Oracle endpoint specifically when handling the encoded ROWID (manually processing the Base64-encoded data). To avoid potential pipeline failures, it is recommended to downgrade the Generic JDBC Snap Pack to the previous version until the issue is resolved.

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:

Generic JDBC: With the 439patches29008 JDBC Snap Pack version, existing pipelines using the Generic JDBC Execute and Select Snaps may experience issues when connecting to the Oracle endpoint, specifically when handling the encoded ROWID (manually processing the Base64-encoded data). To avoid potential pipeline failures, it is recommended to downgrade the Generic JDBC Snap Pack to the previous version until the issue is resolved.

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.

Upgrading to this Release

Info

To use the new SnapLogic features and Snaps in the current GA release, ensure that your Snaplexes are upgraded to the recommended version: main-28272 - 4.39 GA (Recommended).

All Snaplexes on older versions will be upgraded to the recommended version during the mandatory automatic upgrade, which is scheduled for 3 PM (PDT) on Saturday, . For other Snaplex versions released this year, view the SnapLogic Release calendar.

...

  • System Configuration now includes the Git Integration page for selecting a Git provider. This supports continuous integration and continuous development (CI/CD) across different environments. Learn more.

    image-20241101-072520.png
  • In the Security section, configure Enhanced Account Encryption (EAE) from the Account encryption page. With a subscription to EAE and use of a Groundplex, sensitive account data is encrypted with a public key in the SnapLogic domain control plane and decryped decrypted with a private key on the Groundplex. Learn more.

    account-encryption.png

  • In the Application settings section, configure Asset catalog visibility. The Asset catalog is available to enterprise SnapLogic customers by request. Learn more.

    image-20241106-104259.png

...

...

...

  • On the APIM Metrics/API Dashboard, Alerts no longer display the error, unable to instantiate policy.

AutoSync

New Features

The new SQL Server Bulk Load endpoint provides better performance for data pipelines that synchronize large datasets. This endpoint requires:

...

The data pipeline must run on a Groundplex configured to use the Microsoft SQL Server Bulk Copy Utility, bcp. Before using this endpoint in an AutoSync data pipeline, you must install the utility on each Groundplex node.

...

New Features

  • The new SQL Server Bulk Load endpoint provides better performance for data pipelines that synchronize large datasets. This endpoint requires:

    • The data pipeline must run on a Groundplex configured to use the Microsoft SQL Server Bulk Copy Utility, bcp. Before using this endpoint in an AutoSync data pipeline, you must install the utility on each Groundplex node.

    • The 438patches28952 AutoSync Snap Pack. Refer to AutoSync settings for information on selecting a Snap Pack for a data pipeline.

Fixed Issues

  • 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.

Documentation Enhancements

...

New Content

  • Enhanced the OAuth 2.0 Client Credentials article with an Okta integration example.Node Metrics

Monitor

Enhancements

  • The Integration catalog, available to enterprise SnapLogic customers by request, is now the Asset catalog. It includes the following enhancements:

    • With the new API described in the Platform section, you can add custom metadata columns to the table of tasks and add, update, or delete existing custom metadata values from a task.

    • With the new configuration described in the Admin Manager section, you can allow all users view-only access to the Asset catalog or restrict it to admins.

    • The new Pipelines tab displays standard pipeline metadata:

      catalog-pipelines-tab.png
    • Task details are easier to read, with important information moved to the header and execution statistics split out into a new tab:

      catalog-task-general-tab.png
    • The Custom tab on the Task details pane includes the ability to edit custom metadata values:

      catalog-task-edit-metadata2.png

...

  • The Asset catalog Edit metadata functionality in the Custom tab of task details has an issue. When editing, if you click Clear to remove an existing value and then click Cancel, the value is deleted instead of being retained as expected.
    Workaround: Re-enter the cleared value and click Save.

  • The average number of documents processed for pipelines that contain a BigQuery Execute Snap is being incorrectly reported as zero. This impacts both the Asset catalog and the Execution overview.

  • In the Asset catalog Pipelines tab, when you filter by the Path column, a search might not return all pipelines that match.

  • The Asset catalog Execution statistics tab for task and pipeline details currently displays no data.

Fixed Issues

  • The Node status and Node type filters are no longer missing from the System overview node view.

  • The documentation Graph descriptions page clarifies which graphs represent total values and which show the average percentage of the value.

...

Fixed Issues

  • The runtime pusher (the mechanism by which the pipelines are initialized before they process data) was improved for better node performancebetter node performance.

  • Pipelines were failing because the Snaplex JCC ran out of the connections, resulting in the error: Timeout waiting for connection from pool.

  • Pipeline executions were taking longer due to the slow preparation of the pipelines.

  • On the APIM Metrics/API Dashboard, alerts were displaying the error: unable to instantiate policy.

RFC Compliance Enforcement

...

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.

...

  • API Suite:

    • Enhanced the GraphQL Client Snap with the Include extensions checkbox to support extensions that enable you to access query content and extension data in a structure similar to the GraphQL response. The non-standard fields in the GraphQL response are now ignored to avoid a possible error.

    • The GraphQL Client Snap now includes an improved error-handling mechanism that emulates how errors are reported in the raw GraphQL response. This enhancement provides additional context and pagination to the error output, which was previously limited to one page. Learn more.

  • Amazon S3:

    • Enhanced the S3 Download Snap with an Enable Staging checkbox that enables you to download an S3 object into a local temporary file. This enhancement addresses the cases where some downstream Snaps take longer to process large volumes of data, potentially causing a connection reset error and pipeline failure.

  • Flow:

    • Added the PipeLoop Snap that enables you to loop on pipeline executions based on a stop condition or iteration limit. The execution of this Snap enables the parent pipeline to control and manage iterative processes using the child pipeline for scenarios where repeated processing is needed until a specific stop condition is met.

  • Kafka:

    • Enhanced the Kafka MSK IAM Account to support Cross-Account IAM Access on Amazon MSK Cluster configured through the Transit Gateway and multi VPC Peering.

    • Enhanced the Kafka MSK IAM Account to support debugging for the IAM configuration. When you enable the IAM debugging (Global properties and Logging Level) in the Snaplex configuration, the account logs the IAM credential identity in the Snaplex log. Learn more.

  • MongoDB:

    • Enhanced the MongoDB Replica and Mongo ReplicaSet Dynamic Accounts to define read preference options when querying data. The default option is Primary, so you cannot allocate the read load to the secondary node. Note that the Secondary preferred mode is not supported for the MongoDB Execute Snap.

  • RabbitMQ:

    • Removed the Route connection errors checkbox from the RabbitMQ Producer and RabbitMQ Consumer Snaps. As a result, any existing RabbitMQ pipelines that are configured with Route connection errors checkbox enabled will stop functioning as before.

      Suggested workaround

      To run your pipelines successfully, you must manually Route the errors to the error view under the Views tabThis change should not impact your existing pipelines because the Route Error Data to Error View is now enabled by default.

    • Added 5672, the default RabbitMQ server value, for the Port field in the RabbitMQ Account.

  • Tableau:

    • Enhanced the Tableau Account and Tableau REST Account with Personal Access Token (PAT) authentication for flexibility and security of Tableau integrations. This enhancement ensures compatibility with MFA (Multi-Factor Authentication) or SSO (Single Sign-on) environments. PAT authentication is the default authentication type for the Tableau REST Account.

...