Category
Data Sources
Product Version
8.0
Redshift Content Breaks After 8.0.1 Upgrade
Completed
After upgrading to 8.0.1 all of my Redshift content is broken! In the logs I'm seeing:
YF:2019-02-28 22:11:14:ERROR (MIReportProcess:runAction) - Error: org.postgresql.util.PSQLException: ERROR: type "e" does not exist
org.postgresql.util.PSQLException: ERROR: type "e" does not exist
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2440)
at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2183)
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:308)
at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:441)
at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:365)
at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:307)
at org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:293)
at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:270)
at org.postgresql.jdbc.PgStatement.executeQuery(PgStatement.java:224)
at org.postgresql.jdbc.PgDatabaseMetaData.getTables(PgDatabaseMetaData.java:1316)
at com.hof.pool.DBUtil.getTables(DBUtil.java:549)
at com.hof.mi.process.MIReportProcess.A(MIReportProcess.java:5837)
at com.hof.mi.process.MIReportProcess.loadTables(MIReportProcess.java:5588)
at com.hof.mi.web.action.MIDataSourceEditAjaxAction.runAction(MIDataSourceEditAjaxAction.java:141)
at com.hof.web.action.AjaxAction.execute(AjaxAction.java:130)
The same problem 
An upgrade to the packaged PostgreSQL Driver in Yellowfin 8.0.1 causes incompatibility with Redshift Data Sources and will result in broken content after upgrading.
It's recommended to instead use the Redshift specific driver, available here. I recommend using the 4.1 driver to utilize the Amazon Redshift Data Source option.
You can use this procedure to upload the driver.
JDBC 4.0 / 4.1 (Recommended) :
With these versions you can create an Amazon Redshift Data Source directly. Simply click the JDBC Driver drop-down and select 'RedShift 4.x Driver.' Enter your connection details as normal and test your connection.
JDBC 4.2 :
This will require you to use a 'Generic JDBC Data Source,' which requires you to obtain and craft the JDBC URL as per the specifications on the download page.
Switching Your Data Source:
Once you have done this, you'll want to alter the data source of your content to target this new Redshift Source. It's recommended to ensure you have good back ups of the Yellowfin Configuration Database prior to making any large changes such as this. The easiest method to alter the target Data Source would be to export your Views and use the Import > Replace option. During the import you can choose your new Redshift Data Source as the target for these Views. More information on this is available here.
And as always, please let us know if you encounter any issues!
Thanks,
Ryan
An upgrade to the packaged PostgreSQL Driver in Yellowfin 8.0.1 causes incompatibility with Redshift Data Sources and will result in broken content after upgrading.
It's recommended to instead use the Redshift specific driver, available here. I recommend using the 4.1 driver to utilize the Amazon Redshift Data Source option.
You can use this procedure to upload the driver.
JDBC 4.0 / 4.1 (Recommended) :
With these versions you can create an Amazon Redshift Data Source directly. Simply click the JDBC Driver drop-down and select 'RedShift 4.x Driver.' Enter your connection details as normal and test your connection.
JDBC 4.2 :
This will require you to use a 'Generic JDBC Data Source,' which requires you to obtain and craft the JDBC URL as per the specifications on the download page.
Switching Your Data Source:
Once you have done this, you'll want to alter the data source of your content to target this new Redshift Source. It's recommended to ensure you have good back ups of the Yellowfin Configuration Database prior to making any large changes such as this. The easiest method to alter the target Data Source would be to export your Views and use the Import > Replace option. During the import you can choose your new Redshift Data Source as the target for these Views. More information on this is available here.
And as always, please let us know if you encounter any issues!
Thanks,
Ryan
UPDATE - This issue has been resolved in 9.8.2 release -
UPDATE - This issue has been resolved in 9.8.2 release -
Replies have been locked on this page!