Premium Feature — Available in the Professional and Enterprise Editions of LabKey Server. Also available as an Add-on to the Starter Edition. Learn more or contact LabKey.

This topic explains how to configure an Amazon Redshift database as an external data source.

The Redshift Driver

Beginning with the 21.3 (March 2021) release of LabKey Server, an appropriate version of the Redshift JDBC driver is bundled with the LabKey Redshift module.

Upgrade Changes for version 21.3 (March 2021)

You must delete any Redshift drivers and dependencies previously installed in the CATALINA_HOME/lib directory to avoid conflicts with the bundled driver. LabKey Server will fail to start if it detects an old Redshift driver in CATALINA_HOME/lib.

Tomcat Configuration

Add a <Resource> element, to your installation's labkey.xml configuration file. Use the configuration template below as a starting point. Replace USERNAME and PASSWORD with the correct credentials.

<Resource name="jdbc/$DATASOURCE_NAME" auth="Container"
validationQuery="SELECT 1"/>

Define a New Schema

Now define a new schema from the Redshift data source. For details see Set Up an External Schema.

Supported Functionality

Most queries that would work against a PostgreSQL data source will also work against a Redshift data source.

Of the known differences most are due to limitations of Redshift, not the LabKey SQL dialect, including:

  • GROUP_CONCAT is not supported (Redshift does not support arrays).
  • Recursive CTEs are not supported; but non-recursive CTEs are supported.
  • Most PostgreSQL pass-through methods that LabKey SQL supports will work, but any involving binary types, such as string encode(), will not work.

Related Topics


Was this content helpful?

Log in or register an account to provide feedback

expand all collapse all