MySQL agent changelog

GSSD-617/619: Fixed missing logic to handle Update operations by splitting into Delete and Insert actions for key changes;

GSSD-611: Fix date mapping on MySQL using datetime data type as default;

Added support for source agent caching;

Improved performance of the agent during bulk loads;

GSSD-580: The agent properties now allow for zeroDateTimeBehavior to easily be set without manually editing the connection string;

Fixed bulk operations not working when a column default is null;

Updated vendor libraries;

Added support for bulk copy;

Fixed an issue that could have caused the agent to send disconnect from the BinLog streaming session.

Fixed binlog type casting;

GSSD-459: Fixed an issue that could cause duplicated columns to be diplayed wihin the Fields editor’s tab when a foreign key is declared;

GSSD-444: Fixed MySQL agent not able to parse an incoming Short value from the BinLog;

GSSD-445: Fixed MySQL agent not able to resume the BinLog processing after all entities within the same pipeline are set into pause and the server is restarted;

Fixed MySQL deserialization for values of columns with type JSON, GEOMETRY, TEXT, TINY_TEXT, MEDIUM_TEXT, LONG_TEXT;

Fixed MySQL wrong usage of Gluesync schema name in some queries;

Added useCursorFetch parameter to connection string in MySQL agent;

GSSD-388: Added flag for zero date conversion to null (when used in conjunction with the ALLOW_INVALID_DATES flag);

Added allowPublicKeyRetrieval parameter to the connection string;

Fixed an issue that could have caused the agent to send duplicated CDC messages;

Fixed a bug that could have caused the agent to halt the replication in certain scenarios, forcing it to wait for a manual restart;

Added support for MySQL 8.4+