2021_06 Bundle¶

DESCRIBE SECURITY INTEGRATION Command: New Properties for Snowflake OAuth¶

With this release, the output of the DESCRIBE INTEGRATION command for Snowflake OAuth security integrations includes two new properties:

Cloned Tables: Change to How Sequences are Referenced¶

With this release, when a database or schema is cloned and it contains a table that references a sequence in the same database/schema, the cloned table references the cloned sequence in the cloned object.

Previously

When a database or schema was cloned that contained a table that referenced a sequence in the same database/schema object, the cloned table continued to reference the original sequence in the source object.

Currently

The cloned table references the cloned sequence in the cloned database/schema.

DESCRIBE USER / SHOW USERS Commands: New DEFAULT_SECONDARY_ROLES Value in Output¶

With this release, the output of the DESCRIBE USER and SHOW USERS commands includes a new DEFAULT_SECONDARY_ROLES value. The value is displayed as a row in the DESCRIBE USER output and as a column in the SHOW USERS output.

This value is added to support future functionality.

DESCRIBE INTEGRATION / SHOW INTEGRATIONS Commands: Comment Included in Output¶

With this release, the output of the DESCRIBE INTEGRATION and SHOW INTEGRATIONS commands change as follows:

Previously

The CREATE INTEGRATION and ALTER INTEGRATION commands supported specifying a comment; however, the comment was not always displayed in the output of certain commands:

• DESCRIBE INTEGRATION output did not include a COMMENT row.

• SHOW INTEGRATIONS output did not include a COMMENT column.

Currently

The commands display comments in the appropriate output row/column.

This current behavior applies to all types of integrations: API, notification, security, and storage.

SHOW MANAGED ACCOUNTS Command: New Account Name Field in Output¶

With this release, the output of the SHOW MANAGED ACCOUNTS command changes as follows:

Previously

The url column displayed the account locator URL in the following format:

<account_locator>.snowflakecomputing.com

Currently

The url column displays the account name URL, the new URL format introduced in the Organizations feature. The new URL has the following format:

<org_name>-<account_name>.snowflakecomputing.com

In addition, the output includes a new column, account_locator_url, to display the account locator URL.

CURRENT ACCOUNT Function: Change to Account Name Returned in Output¶

With this release, the output of the CURRENT_ACCOUNT function changes as follows:

Previously

The function returned the account locator (formerly referred to as the account name) for the user's current session.

The account locator is a read-only identifier that is assigned to the account when it is provisioned and cannot be changed.

Currently

The function returns the new version of the account name, introduced in the Organizations feature.

Account names uniquely identify an account within an organization and can be changed by users with the ORGADMIN role.

COPY INTO <location> Command: NUMBER Column Mapping to Parquet Data Type¶

When NUMBER columns in Snowflake tables are unloaded to Parquet files, the corresponding columns in the files have the equivalent DECIMAL logical data type.

With this release, the criteria for determining the precision and scale of the columns in the unloaded Parquet files has changed as follows:

Previously

The DECIMAL column in the Parquet files had the lowest precision that could represent the range of values in the column. This behavior could lead to inconsistent data types among the unloaded files, making the files unusable with external tools.

Currently

The DECIMAL column in the Parquet files has the same precision and scale as the source column in the Snowflake table.

For example, if the table column has the default precision and scale (NUMBER(38, 0)), then the same column is unloaded to a DECIMAL(38, 0) column in the Parquet files.

CREATE TABLE ... LIKE Command: Constraints Not Included for Tables Created from Shared Tables in Consumer Accounts¶

With this release, the CREATE TABLE ... LIKE command changes as follows:

Previously

If the command was used in a consumer account to create a new table from a shared table with constraints, the new table included the constraints.

Currently

Any new table created from a shared table with constraints does not include the constraints.

You can use the GET_DDL function on the new table created from the shared table to verify whether the constraints were included.

Snowflake Connector for Python: Changes to the write_pandas() Function¶

Version 2.5 of the Snowflake Connector for Python changes the way in which the write_pandas() function quotes column names: