You are viewing documentation for an older version.

Click here to view the latest documentation.

Version 0.15

10 July 2024 Schema version: 69

What’s New

• Support for key-pair authentication in Snowflake for enhanced security.
• Schema has been updated from 67 to 69.

Improvements

• Replaced ROW_NUMBER() OVER(ORDER BY 1) with ROW_NUMBER() OVER() for Redshift and BigQuery. This eliminates an unnecessary ORDER BY first column.

Known Issues

• When using the CLI: You will have to manually make changes in the siteconfig.yaml file to add a Snowflake connection with key-pair authentication.
• RudderStack does not support accessing input sources in a different project for the BigQuery warehouse.
• Linux users might see this warning for all command runs - you can ignore it: WARN[0000]log.go:228 gosnowflake.(*defaultLogger).Warn DBUS_SESSION_BUS_ADDRESS envvar looks to be not set, this can lead to runaway dbus-daemon processes. To avoid this, set envvar DBUS_SESSION_BUS_ADDRESS=$XDG_RUNTIME_DIR/bus (if it exists) or DBUS_SESSION_BUS_ADDRESS=/dev/null.
• Redshift: If two different users create material objects on the same schema, RudderStack gives an error during cleanup when trying to drop views created by the other user, like user_var_table.
• pb validate access command does not work for BigQuery.
• pb insert does not work for Redshift, Databricks, and BigQuery.
• Cross database references can fail on Redshift for a few clusters.
• If you are referring a public package in the project and get ssh: handshake failed error, then you’ll have to manually remove the entire folder from WhtGitCache to make it work.
• The code for validity_time is redundant and should be removed.
• Timegrains is an experimental feature. There might be some undiscovered issues.
• While creating Activations, validation for Redshift does not work correctly in the RudderStack dashboard.