Versions Compared

Version Old Version 53 New Version 54
Changes made by

Ruth Stento

Ruth Stento

Saved on

Key

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

...

  • 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

...

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

...

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.

...