Snowflake Connector for Google Analytics Raw Data release notes¶

Behavior changes¶

Not applicable.

New features¶

• The procedure UPDATE_CONNECTION_CONFIGURATION was introduced. It can be used for re-authentication purposes. Connector has to be paused to use this procedure. Currently it is only available from the worksheet and takes one argument type of variant composed of fields: external_access_integration, security_integration and secret.

Bug fixes¶

Not applicable.

Behavior changes¶

Not applicable.

New features¶

Not applicable.

Bug fixes¶

• Fixed an issue with disrupted scheduling of ingestions during execution of dispatcher task.

Behavior changes¶

Not applicable.

New features¶

Not applicable.

Bug fixes¶

• Fixed an issue where changing the ingestion schedule while the dispatcher task was running could lead to temporary duplication of the dispatcher task.

Behavior changes¶

• The connector now requests permission to EXECUTE MANAGED TASK. This is in preparation for internal monitoring features that will help us discover and address issues earlier.

New features¶

Not applicable.

Bug fixes¶

• Fixed an issue where changing the ingestion schedule while the dispatcher task was running could corrupt the internal state of the connector so that it would not be able to schedule further ingestions.

Behavior changes¶

Not applicable.

New features¶

• A number of optimizations made to scheduling ingestions and ingesting itself. This should result in slightly lower credit consumption, as well as increased ingestion throughput, especially on tables with fewer than one million records.

• The connector now supports mixed-case and lowercase secret names.

Bug fixes¶

• Ingestions should no longer fail due to issues with refreshing the access token. This may very rarely still occur for particularly large tables, but will always be re-tried by the connector automatically.

• Added validation to prevent enabling the same Google Analytics property ingestion from multiple Google Cloud Platform projects.

• Enabling multiple properties at once is now more resilient against issues with BigQuery connectivity. It will only fail the properties for which it couldn’t connect to BigQuery, and successfully enable all the others.

Behavior changes¶

• Several stored procedures, meant specifically for early user interface, access were removed. These stored procedures were generally not documented, and not part of our public API, but they may have been visible when listing procedures exposed by the connector. There’s no change in how the connector works, or how it should be operated.

• The procedure CONFIGURE_CONNECTION now requires an additional parameter security_integration with the name of the security integration created for the connector. This applies only for worksheet-based setups. If you’re setting the connector up via the user interface, this change is transparent to you.

New features¶

• Updated links to the connector’s documentation.

Bug fixes¶

• Improved reading tables available in BigQuery to ensure we only look at Google Analytics export tables, and filter out similarly-named tables. This issue could sometimes cause enabling new properties, or ingesting enabled properties to fail.

Behavior changes¶

Not applicable.

New features¶

Not applicable.

Bug fixes¶

Not Applicable