This section provides information on how to enable Redshift connectivity and create one or more connections to Redshift sources.
- Amazon Redshift is a hosted data warehouse available through Amazon Web Services. It is frequently used for hosting of datasets used by downstream analytic tools such as Tableau and Qlik. For more information, see https://aws.amazon.com/redshift/.
Before you begin, please verify that your Trifacta® environment meets the following requirements:
NOTE: In the Admin Settings page are some deprecated parameters pertaining to Redshift. Please ignore these parameters and their settings. They do not apply to this release.
- S3 base storage layer: Redshift access requires use of S3 as the base storage layer, which must be enabled. See Set Base Storage Layer.
- Same region: The Redshift cluster must be in the same region as the default S3 bucket.
- Integration: Your Trifacta instance is connected to a running environment supported by your product edition.
- Deployment: Trifacta platform is deployed either on-premises or in EC2.
- When publishing to Redshift through the Publishing dialog, output must be in Avro or JSON format. This limitation does not apply to direct writing to Redshift.
You can publish any specific job once to Redshift through the export window. See Publishing Dialog.
- Management of nulls:
- Nulls are displayed as expected in the Trifacta application.
When Redshift jobs are run, the UNLOAD SQL command in Redshift converts all nulls to empty strings. Null values appear as empty strings in generated results, which can be confusing. This is a known issue with Redshift.
You can create Redshift connections through the following methods.
Tip: SSL connections are recommended. Details are below.
Create through application
Any user can create a Redshift connection through the application.
- Login to the application.
- In the menu, click Settings menu > Connections.
- In the Create Connection page, click the Redshift connection card.
Specify the properties for your Redshift database connection. The following parameters are specific to Redshift connections:
Property Description IAM Role ARN for Redshift-S3 Connectivity
(Optional) You can specify an IAM role ARN that enables role-based connectivity between Redshift and the S3 bucket that is used as intermediate storage during Redshift bulk COPY/UNLOAD operations. Example:
For more information, see Configure for EC2 Role-Based Authentication.
For more information, see Create Connection Window.
Enable SSL connections
To enable SSL connections to Redshift, you must enable them first on your Redshift cluster. For more information, see https://docs.aws.amazon.com/redshift/latest/mgmt/connecting-ssl-support.html.
In your connection to Redshift, please add the following string to your Connect String Options:
Save your changes.
Create via API
For more information, see API Connections Create v4.
Import a dataset from Redshift. Add it to a flow, and specify a publishing action. Run a job.
NOTE: When publishing to Redshift through the Publishing dialog, output must be in Avro or JSON format. This limitation does not apply to direct writing to Redshift.
For more information, see Verify Operations.
After you have run your job, you can publish the results to Redshift through the Job Details page. See Publishing Dialog.
This page has no comments.