Preview — 8.44 Release Notes

Attention

Content in this page is available in advance of the completion of the 8.44 release, which is currently either pending or in progress.

The release is scheduled to complete on November 19 (subject to change).

Features, updates, or behavior changes described in this page might not become available in your account(s) until the completion of the release.

For updates to these release notes, see Release notes change log.

New features

Outbound private connectivity for Snowflake features

By default, Snowflake features that generate outbound network traffic from Snowflake to a cloud platform traverse the public Internet. You can now create private endpoints in Snowflake to access the cloud platform using the platform’s private connectivity solution rather than the Internet. This lets you access cloud platform services privately and securely from Snowflake.

With this release, outbound private connectivity is now available for the following Snowflake features:

Visual Studio Code extension for Snowpark Python — General availability

With this release, Snowflake is pleased to announce that the Snowflake Visual Studio Code extension now integrates with Snowpark Python to provide authoring and debugging features for Snowpark Python code.

These new features include:

  • Inline debugging of Snowpark Python functions.

  • Syntax highlighting and autocomplete suggestions for Snowflake SQL in Python strings within Python files or notebook cells.

  • Syntax highlighting and bracket autocomplete of Jinja templates in Snowflake SQL.

Extensibility updates

External network access for Azure Gov regions — General availability

With this release, we are pleased to announce general availability of external network access in Azure Gov regions. Access network locations external to Snowflake from within procedure and UDF handler code is now generally available in all regions.

Data lake updates

Specify an external ID for SIGV4 REST catalog integrations

With this release, we are pleased to announce support for specifying an external ID when you create a catalog integration for Apache Iceberg™ REST that uses SIGV4 authentication.

Specifying an external ID lets you use the same IAM role across multiple catalog integrations. This can be useful in testing scenarios when you need to recreate or replace a catalog integration many times.

Release notes change log

Announcement

Update

Date

Release notes

Initial publication (preview)

15-Nov-24