This is a temporary solution, but is no longer the recommended practice. Perhaps this setting is being ignored when the graph is run via kitchen.sh? I've been able to run the graphs in spoon on my Mac even without this setting, but when run from kitchen they always fail.įor now I have reverted to using the Postgres driver for both since Redshift was originally based on Postgres. I've tried enabling this within PDI's database connection options window with a Parameter of OpenSourceSubProtocolOverride and a value of true, but this did not resolve the issue. Leveraging this driver, Collibra Catalog will be able to register database information and extract the structure of the source into its schemas, tables and columns. (look for OpenSourceSubProtocolOverride). The Amazon Redshift JDBC driver can be used in the Collibra Catalog in the section ‘Collibra provided drivers’ to register Amazon Redshift sources.Apparently this is somewhat of a known issue and has been fixed by Amazon with a new param that can be passed in the Redshift connection string: I've tested this with many combinations of the JDBC drivers provided by both projects without resolution.
When using 2 database connections in the same graph, were one points to a Postgres database and the other a Redshift database (using JDBC connections for both), Redshift clobbers the Postgres driver causing the graph to fail. Within SQL Developer, go to Tools > Preferences > Database > Third Party JDBC Drivers (for Mac, this is Oracle SQL Developer > Preferences Database > Third.
