Snowflake Connector for MySQL release notes¶
This topic provides release notes for the Snowflake Connector for MySQL. For additional information, see Snowflake connector for MySQL.
Version 6.8.0 (November 22nd, 2024)¶
Behavior changes¶
Increased the minimum schedule interval to 15 minutes.
Pre-existing 10-minute intervals remain unchanged. Snowflake recommends setting them to at least 15 minutes.
The operational warehouse will now suspend when there is no data traffic from the source database for more than 5 minutes.
The
Killing agent on shutdown container
error message will not show when triggering the agent’s shutdown. Instead, the following message will be logged on the INFO level:Stopping the agent on the container shutdown signal
.
New features¶
The
PUBLIC.REMOVE_TABLES(DATA_SOURCE_NAME STRING, SCHEMA_NAME STRING, TABLE_NAMES ARRAY)
procedure enables the removal of multiple tables with one call.
Bug fixes¶
The operational warehouse will now correctly suspend when all data sources are switched to a scheduled mode.
The agent will no longer restart when the logging rate is too high.
Fixed replication errors when the
DEFAULT_DDL_COLLATION
parameter for account is set.
Version 6.6.1 (October 3rd, 2024)¶
Behavior changes¶
The maximum connection pool size to source databases has been increased to 7.
New features¶
Not applicable.
Bug fixes¶
The agent no longer stops after encountering data source connectivity issues.
Version 6.6.0 (September 17th, 2024)¶
Behavior changes¶
Not applicable.
New features¶
You can now configure the agent through environment properties in addition to using
snowflake.json
anddatasources.json
for configuration.You can now pass the private key contents through the
snowflake.private-key
property orSNOWFLAKE_PRIVATEKEY
environment variable.
For more information, see Configure and run the agent.
Bug fixes¶
When schema introspection fails the operational warehouse suspends in the scheduled mode.
Fixed a bug where some commands to stop table replication were ignored in a few cases.
Fixed a bug where some source tables couldn’t be added to the replication and returned the error message
Tables are not ready to be re-added
.
Version 6.5.0 (August 27th, 2024)¶
Behavior changes¶
Not applicable.
New features¶
Not applicable.
Bug fixes¶
In continuous mode, the compute warehouse will now be able to suspend if there is no data to merge into destination tables.
Fixed agent failure when MySQL server enforces secure connection
Version 6.4.0 (August 15th, 2024)¶
Behavior changes¶
Not applicable.
New features¶
Not applicable.
Bug fixes¶
Corrected an issue where the connector could become stuck in a state where commands were not delivered to the agent.
Version 6.3.2 (July 15th, 2024)¶
Initial release of version 6.3.2.
Behavior changes¶
Not applicable.
New features¶
Not applicable.
Bug fixes¶
Fixed handling of deleted columns in subsequent schema changes.
Fixed compute warehouse not suspending in scheduled mode.
Fixed validation of reserved column names to be case insensitive.
Fixed MySQL tables failing replication on huge transactions.
Version 6.3.0 (July 11th, 2024)¶
Initial release of version 6.3.0.
Behavior changes¶
Not applicable.
New features¶
Not applicable.
Bug fixes¶
Not applicable.