Issue with using the newest Amazon Redshift Drivers (1.2.7) within your Jobs

Symptoms

Amazon has updated their JDBC driver for Redshift and Postgres, which are available at this time. After getting the new drivers and adding them to Studio, when attempting to run a Job, the following errors may comes up in your CommandLine or Studio:

 

Connection to dev-edw-postgres.<Hostname>.us-east-1.rds.amazonaws.com:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections. 
at org.talend.core.model.metadata.builder.database.JDBCDriverLoader.getConnection(JDBCDriverLoader.java:195) 

can not find class :org.postgresql.Driver
!STACK 0
org.talend.utils.exceptions.MissingDriverException: can not find class :org.postgresql.Driver

 

Diagnosis

The newest JDBC driver has been downloaded, and Studio and CommandLine have been updated, but they still reference the old driver when communication is sent out to the Redshift or Postgres instance. This will cause a communication and compiling issue, as CommandLine is expecting the newest driver, but when the jars are being referenced, the old driver is forced into the package, causing compiling errors.

 

Solution

This issue has been reported, and will be fixed in future versions of Talend. For those customers that are using current versions of Talend, there are patches available for versions 6.3.1 and 6.2.1. To request the patch and get more information on the issue, please contact Talend Support.

 

Amazon RDS and Postgres JDBC drivers:

http://docs.aws.amazon.com/redshift/latest/mgmt/configure-jdbc-connection.html#download-jdbc-driver

 

Link to original bug report:

https://jira.talendforge.org/browse/TDI-39514

 

Version history
Revision #:
4 of 4
Last update:
‎09-29-2018 12:11 AM
Updated by: