In this article
| Table of Contents |
|---|
Overview
The Redshift Snap Pack will use uses the Amazon Redshift JDBC driver com.amazon.redshift.jdbc42.Driverdriver as the default driver class beginning from the March 2023 release. This upgrade is backward - compatible. The existing pipelines configured either with the PostgreSQL JDBC driver or the Redshift JDBC driver will continue to work as expected and the . The new pipelines will use the Amazon Redshift Driver JDBC driver as the default driver. However, the support for the PostgreSQL JDBC driver class will end by the November 2023 release.
Important:
SnapLogic will support providing fixes for the issues you might encounter with accounts using that use the PostgreSQL JDBC driver in the Redshift Snap Pack until November 2023.After only until November 2023, after which SnapLogic will no longer support the PostgreSQL drivernot provide support. Therefore, in such scenarios, you must we recommend that you migrate from the PostgreSQL JDBC driver to the Redshift JDBC driver by November 2023.
| Multiexcerpt include macro | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Migrating to the Amazon Redshift
...
JDBC driver
To migrate from the PostgreSQL to the Redshift JDBC driver as the default driver, update the JDBC Driver Class in the Account settings from “org.postgresql.Driverdriver” to "com.amazon.redshift.jdbc42.Driverdriver" in your existing accounts.:
...
JDBC Driver Configuration Scenarios in Redshift Accounts
If your account configuration uses the following combination of JAR files, driver classes and JDBC URLs, your accounts Your pipelines might use a combination of JDBC drivers, classes, and URLs of either the PostgreSQL or the Amazon Redshift JDBC. Here are the configuration scenarios that are authenticated successfully.
| Panel | ||
|---|---|---|
| ||
|
...
|
JDBC Driver JAR | JDBC Driver Class | JDBC URL | Authentication |
Redshift (default/manual) |
| Jdbc | Authenticates successfully when the:
|
Redshift (manual upload) |
| Jdbc | Authenticates successfully using the manually uploaded JAR file and manually specified JDBC URL. |
PostgreSQL (default/manual) |
| Jdbc | Authenticates successfully when the:
|
PostgreSQL (manual) |
|
| Authenticates successfully using the manually uploaded JAR file and manually specified JDBC URL. |
Redshift JAR(manual) |
|
| Authenticates successfully using the default PostgreSQL JAR file. |
PostgreSQL JAR(manual) |
|
| Authenticates successfully using the default Redshift JAR file. |
If your account configuration uses one of the following combination combinations of JAR files, driver classes, and JDBC URLs, then your accounts account cannot be authenticated because of the misaligned JDBC driver class and JDBC URL.
JDBC Driver JarJAR | JDBC Driver Class | JDBC UrlURL | Authentication |
Redshift JAR |
|
| Authentication fails. |
Redshift JAR |
|
| Authentication fails. |
PostgreSQL JAR |
|
| Authentication fails. |
PostgreSQL JAR |
|
| Authentication fails. |
Behavior Change
...
Display of labels in the output for the Redshift Select Snap
For the Redshift Select Snap, when you configure Output fields and deselect the Match data types checkbox, the display of lables the label name for the Output fields timestamptz data type in the output preview varies with the two JDBC drivers. For instanceexample, consider the following configuration of the Output fields in the Redshift Select Snap.
...
On validation, notice the difference in the label name in the output preview.
...
With the PostgreSQL Driver configured in the accountdriver, the Snap dislays displays the labels as configured in the Redshift Select Snap .settings:
...
With While with the Redshift Driver configured in the accountJDBC driver, the Snap prefixes Redshift to the Timestamp label. This does not impact the performance of the Snap.
...
Batch Size
...
The behavior of the Snap remains the same when you select the Match data types checkbox, regardless of using the PostgreSQL or the Redshift driver—the label names are displayed as configured in the Snap settings.