| Table of Contents | ||
|---|---|---|
|
Overview
We are rolling out an important update in the JDBC Snap Pack. This update is about includes upgrading the jOOQ library to version 3.17.x, which includes contains several improvements, optimizationsperformance optimization, and key changes that may impact your current integrations with SnapLogic. This FAQ document provides the reasons behind this update, the expected impact, the timelines for the upgrade, the affected databases, and the expected behavior changes.
What is happening?
The jOOQ library for the JDBC Snap Pack is upgraded from v3.9.1 to v3.17.x.
Why are we upgrading the JDBC jOOQ library?
To improve security, compatibility, performance, stability, and reliability.
What is the timeline for this upgrade?
The upgrade to jOOQ 3.17.x for the JDBC Snap Pack will be rolled as per the following timelines:
Early availability phase/Latest Release: This phase will allow early adopters to test the new version and provide feedback. You can choose to use the latest version of the Snap Pack for testing and reporting any issues you encounter.
General Availability (GA)/Stable Release: The full upgrade to jOOQ 3.17.x will be available to all with the GA release on February 12, 2025. The stable version is then pushed to all production environments.
Will I be impacted?
Yes, you may be impacted if you use the latest version. If you prefer not to proceed with the jOOQ upgrade, you can revert to the previous working version of the Snap Pack.
What are the key areas affected by this upgrade?
SQL generation and parsing
Database connection pooling
Query performance and execution time
Error and exception handling
Compatibility with some legacy database features
Which databases were tested for the jOOQ upgrade?
Given the various databases in use, we have tested against only specific databases. However, we recommend testing your pipelines in your lower-level environments (development or QA) to ensure compatibility and functionality with your specific database before planning on the production environment.
...
| Info |
|---|
We recommend you investigate your pipelines and check the Snaps downstream of JDBC Snaps for any of the affected scenarios. Update any dependencies that the downstream Snaps might have with respect to the changing error and outputs (especially in expressions) to conform to the new expected errors and outputs. |
Do I need to reconfigure my accounts?
Yes, you need to reconfigure your accounts if the current driver (JARs) is incompatible with the upgraded jOOQ version (v3.17.x). For more details, refer to the breaking changes.
What are the recommended JDBC drivers (JARs) for various databases?
Database | Latest certified and recommended drivers | Dependencies |
SQL Server | mssql-jdbc-11.2.0.jre11.jar | For this driver version, you must set the URL property in the Generic Database Account as |
MySQL | mysql-connector-java-5.1.47.jar (MySQL 5.x.x server version) |
|
Oracle | ojdbc10.jar |
|
Snowflake | snowflake-jdbc-3.13.25.jar |
|
Redshift | RedshiftJDBC42-1.1.17.1017.jar |
|
Postgre SQL | postgresql-42.7.2.jar |
|
Vertica | vertica-jdbc-11.0.0-0.jar |
|
Teradata | 17.20.12 |
|
Cassandra | v4.11.1 |
|
Maria DB | mariadb-java-client-2.6.0.jar |
|
Informix | ifxjdbc.jar |
|
Db2 | db2jcc4.jar |
|
SAP HANA | ngdbc-2.8.14.jar |
|
IBM Db2 i | jt400-20.0.7.jar |
|
Sybase | jconn4.jar |
|
Athena AWS | AthenaJDBC42_2.0.24.1000.jar |
|
Breaking Changes
After the jOOQ library upgrade, we recommend that you use the SnapLogic-certified drivers for your target databases. If you do not use the certified drivers, the previously functioning pipelines might be impacted.
Additionally, we highly recommend that you migrate to dedicated Database Snap Packs (for example, Oracle, SQL Server, MySQL, Redshift) instead of using the Generic JDBC Snap Pack for your integration needs.
Behavior Changes
The following table lists the change in the output messages:
...