/
MySQL Snap Pack

MySQL Snap Pack

In this article

Overview

Use the MySQL Snap Pack to connect to your MySQL database or MySQL-compatible database (like Aurora and MariaDB) and achieve read and write access to its objects. 

Use Snaps in this Snap Pack to:

  • Get list of tables in a database.

  • Lookup records in the target table and return a selected set of fields.

  • Fetch data from a database.

  • Execute SQL statements to delete, update, merge or insert data within a specified table.

Supported Versions 

  • This Snap Pack is tested against:

    • MySQL 8.0.17

    • Amazon Aurora 1.17.2

    • Azure SQL DB 5.6 and 5.7

  • MySQL - Bulk Load Snap supports the following versions:

    • MySQL 8.0.17 

    • MySQL 5.6.34

Known Issues

When MySQL execute Snaps (MySQL - Execute and MySQL - Multi Execute) are followed by MySQL non-execute Snaps, such as MySQL - Insert, MySQL - Merge, and so on, the following error is displayed when executed:

Table definition has changed, please retry transaction.

This happens due to a known issue in the MySql Connector. For more information about this issue, see MySQL Bug #65378.


Snap Pack History

 Click to view/expand
Release Snap Pack VersionDateType  Updates
November 2024main29029 StableUpdated and certified against the current SnapLogic Platform release.

August 2024

main27765

 

Stable

Updated and certified against the current Snaplogic Platform release.

May 2024437patches26298 Latest

Fixed an issue with the MySQL - Multi Execute Snap and the MySQL - Execute Snaps that displayed a null pointer exception when the Snap did not check  null table metadata.

May 2024main26341 StableUpdated the Delete Condition (Truncates a Table if empty) field in the MySQL - Delete Snap to Delete condition (deletes all records from a table if left blank) to indicate that all entries will be deleted from the table when this field is blank, but no truncate operation is performed.
February 2024436patches25659 Latest
  • Fixed an issue with the MySQL- Multi Execute Snap that committed the changes when the Snap was expected to roll back if any query failed and the Number of Retries was more than 0. The Snap now performs a rollback when one or more queries fail.

  • Fixed an issue with the MySQL-Insert Snap that displayed an error when you inserted values such as 128 or more in the Tinyint unsigned datatype when the datatype must accept all the values in the range of 0-255.

  • Fixed an issue with MySQL-Insert Snap that failed to store the Time datatype with precision in the target table when passed from an upstream Mapper Snap in the string format or Date-only date format.

February 2024main25112 StableUpdated and certified against the current SnapLogic Platform release.
November 2023main23721

 

StableUpdated and certified against the current SnapLogic Platform release.

August 2023

main22460

 


Stable

The MySQL - Execute Snap now includes a new Query type field. When Auto is selected, the Snap tries to determine the query type automatically.

May 2023

main21015 

Stable

Upgraded with the latest SnapLogic Platform release.

February 2023432patches19870 Latest

Fixed an issue with the preview data of the MySQL-Execute Snap that displayed the date format as %m %d %Y (without the forward slash '/'). The Snap now displays the date as intended in %m/%d/%Y format after validation.

February 2023main19844 StableUpgraded with the latest SnapLogic Platform release.
November 2022431patches19263 Latest

The MySQL Insert Snap no longer includes the Preserve case-sensitivity checkbox because the database is case-insensitive. The database stores the data regardless of whether the columns in the target table and the input data are in mixed, lower, or upper case.

November 2022main18944 Stable
  • The MySQL - Insert Snap now creates the target table only from the table metadata of the second input view when the following conditions are met:

    • The Create table if not present checkbox is selected.

    • The target table does not exist.

    • The table metadata is provided in the second input view.

September 2022430patches17894 Latest

The MySQL Select Snap now work as expected when the table name is dependent on an upstream input;

August 2022430patches17387 Latest

The following issues are fixed in the MySQL Bulk Load Snap:

  • Writing the first batch of records to a temporary file after the Snap fails. Now the Snap writes to the error view as is the expected behavior.

  • Temporary files generation when a record does not contain a table column. Now, the Snaplex removes the temporary files created along with the directory after the Pipeline execution.

August 2022main17386 StableUpgraded with the latest SnapLogic Platform release.

4.29

main15993

 

Stable

Upgraded with the latest SnapLogic Platform release.

4.28 Patch

428patches15101

 Latest

Fixed an issue with SQL Server - Execute Snap where the Pipeline was failing when there were consecutive execute Snaps with a procedure call, followed by select statements.

4.28main14627 StableUpdated the label for Delete Condition to Delete Condition (Truncates Table if empty) in the MySQL Delete Snap.