Learn more about Installing td-agent on AWS Linux.
You can write job results to your existing Amazon Redshift cluster. For sample workflows on Amazon Redshift for Export, view Treasure Boxes.
This topic contains:
Basic knowledge of Treasure Data, including the TD Toolbelt
An Amazon Redshift cluster setup and running – either a single or multi-node cluster
At least ‘Query only’ privileges to the Treasure Data table to be queried
- When exporting results to Redshift, Redshift tries to convert the column type if the destination table already exists. If a column becomes NULL during conversion, and all records are rejected if the column on Redshift is a NOT NULL field. This may be the case even when the job for exporting results to Redshift was successful, but your Redshift doesn’t get any data.
This connector does not support timestamp/date type data. You need to convert that type of data to string column or Unix timestamp.
Result Output to Redshift can export data to several regions. The following are the supported regions:
us-east-1 (US Standard)
us-west-1 (N. California)
sa-east-1 (São Paulo)
The following regions are not supported:
If you have other regions that you want to support, contact Treasure Data support.
A front-end application streams data to be collected in Treasure Data via Treasure Agent (td-agent). Treasure Data periodically runs jobs on the data, then writes the job results to your Redshift cluster.
The image shows a fairly common architecture that enables data analysts, well versed in using Redshift, to focus on queries and visualizations rather than how to get the data uploaded.
You can limit access to your database by using a list of static IPs. Contact firstname.lastname@example.org if you want to use static IP addresses.
Amazon Redshift Configuration
Amazon Redshift can be configured in single-node mode or multi-node/cluster mode. The multi-node configuration provides more query computation power by means of parallelization of the query execution on the available nodes.
Use the TD Console to Create Your Connection
Create a New Connection
In Treasure Data, you must create and configure the data connection prior to running your query. As part of the data connection, you provide authentication to access the integration.
1. Open TD Console.
2. Navigate to Integrations Hub > Catalog.
3. Click the search icon on the far-right of the Catalog screen, and enter Amazon Redshift.
4. Hover over the Amazon Redshift connector and select Create Authentication.
5. Type the credentials to authenticate.
|Host||The host information of the source database, such as an IP address. can be retrieved from the Redshift configuration page. Typically, the format is: <name>.<instance_id>.<region>.redshift.amazonaws.com. The name is the one provided for the cluster, the instance id is auto-generated by Amazon Redshift upon creation of the cluster, the region is the Amazon availability zone of choice. If you are using an IP address instead of hostname, you must set |
The connection port on the source instance. The PostgreSQL default is 5432.
The port number through which the Redshift server is accessible. “:” is optional and assumed to be 5439 by default. It may vary for multi-node cluster configurations. The actual value can be retrieved from the Redshift cluster detail page.
|User||Username to connect to the source database. The credentials to the Amazon Redshift instance. These credentials are specified when first creating the Redshift cluster and they are different from the S3 public/private access keys.|
|Password||The password to connect to the source database.|
|Use SSL||Check this box to connect using SSL|
|JDBC Connection options||Any special JDBC connections required by the source database (optional).|
The AWS regions in which your Redshift instance is hosted.
Specify the region where your Redshift instance is located. This option is required if your hostname does not contain the region name.
|Socket connection timeout||Timeout (in seconds) for socket connection (default is 300).|
|Network timeout||Timeout (in seconds) for network socket operations. 0 means no timeout.|
|Rows per batch||Number of rows to fetch one time.|
Options that you want to give to the JDBC driver.
For example, you can use these parameterand value fields to define various URL options such as LogLevel or LogPath.
Result output to Redshift supports various options that can be specified as optional URL parameters. The options are compatible with each other and can be combined. Where applicable, the default behavior is indicated.
ssl option determines whether to use SSL or not for connecting to Redshift.
8. Select Continue after entering the required connection details.
9. Name the connection so you can find it later should you need to modify any of the connection details.
10. Optionally, select Share with others, if you would like to share this connection with other users in your organization.
11. Select Done.
Define your Query
- Complete the instructions in Creating a Destination Integration.
Navigate to Data Workbench > Queries.
Select a query for which you would like to export data.
Run the query to validate the result set.
Select Export Results.
- Select an existing integration authentication.
- Define any additional Export Results details. In your export integration content review the integration parameters.
For example, your Export Results screen might be different, or you might not have additional details to fill out:
Run your query.
Validate that your data moved to the destination you specified.
Integration Parameters for Redshift
Name of the database to export the data to.
The name of the database specified at the creation of the Redshift cluster. It can be retrieved from the Redshift cluster detail page.
Name of the table within the database to export the data to.
The name of a table within the database. It may not exist when the query output is executed. If the table does not exist, a table with the specified name is created.
Controls the various ways of modifying the database data.
This is the default mode. The query results are appended to a collection. If the collection does not exist yet, a new collection is created.
This method is atomic.
The replace mode consists of replacing the entire content of an existing table with the resulting output of the query. If the table does not exist, a new table is created.
For the fastest results, we recommend that you have only one **write** connection open to your RDS database table at a time.
The replace mode achieves atomicity (so that a consumer of the table always has consistent data) by performing the following steps in a single transaction:
For the fastest results, we recommend you have only one **write** connection open to your RDS database table at a time.
Truncate mode retains the indexes of the table. With the truncate mode, the system first truncates the existing table to remove all records, then inserts the query results into the existing table without modifying the table’s schema.
If the result output table contains columns whose name or type (or both) mismatches from the schema of the destination table, then the columns are dropped, and they will not get written into the destination table. This is not a problem when the destination table does not exist: a new table will be created with schema matching that of the result output table.
The truncate mode uses a temporary table, hence achieves atomicity of write.
Unlike replace, the truncate mode retains the indexes of the table.
In the update mode, a row is inserted unless it would cause a duplicate value in the columns specified in the “unique” parameter. In such a case, an update is performed instead. A unique parameter is required when using the update mode. If the table does not exist, it will be created.
This mode is atomic because it uses a temporary table to store the incoming data before attempting to insert the data into the actual destination table.
Select to modify the existing data rather than copying it. This can be a big performance gain.
The default value is true.
Controls the schema the target table is located. If not specified, a default schema is used. The default schema depends on the user’s “search_path” setting but it is usually “public”.
The serial_copy option determines whether to upload all the files in order one by one, to avoid some deadlocks that could happen when uploading files parallel.
If you use the TD Toolbelt to run the query that returns the data that you want to have exported to Amazon Redshift:
One Time Export using CLI
Scheduled Export using CLI
If your Redshift doesn’t get any data, even when the job for Result Output to Redshift was successful
Result Output to Redshift tries to convert column type if the destination table already exists. If the conversion fails, the column becomes NULL and all records are rejected if the column on Redshift is NOT NULL field.