
The tRedshiftOutputBulk and tRedshiftBulkExec components can be used together in a two step process
to load data to Amazon Redshift from a delimited/CSV file on Amazon S3. In the first
step, a delimited/CSV file is generated. In the second step, this file is used in the
INSERT statement used to feed Amazon Redshift. These two steps are fused together in the
tRedshiftOutputBulkExec component. The advantage of
using two separate steps is that the data can be transformed before it is loaded to
Amazon Redshift.
Component family |
Databases/Amazon Redshift |
|
Function |
This component receives data from the preceding component, generates a single |
|
Purpose |
As a dedicated component, it allows gains in performance during |
|
Basic settings |
Property Type |
Either Built-In or Repository. Since version 5.6, both the Built-In mode and the Repository mode are |
|
|
Built-In: No property data stored |
|
|
Repository: Select the repository file in which the |
Database settings |
Use an existing connection |
Select this check box and in the Component List click the |
|
Host |
Type in the IP address or hostname of the database server. |
|
Port |
Type in the listening port number of the database server. |
|
Database |
Type in the name of the database. |
|
Schema |
Type in the name of the schema. |
|
Username and Password |
Type in the database user authentication data. To enter the password, click the […] button next to the |
|
Table Name |
Specify the name of the table to be written. Note that only one |
|
Action on table |
On the table defined, you can perform one of the following
|
|
Schema and Edit schema |
A schema is a row description. It defines the number of fields to be processed and passed on Since version 5.6, both the Built-In mode and the Repository mode are |
|
|
Built-In: You create and store the schema locally for this |
|
|
Repository: You have already created the schema and |
|
|
Click Edit schema to make changes to the schema. If the
|
File Generate Setting |
Data file path at local |
Specify the local path to the file to be generated. Note that the file is generated on the same machine where the |
|
Append the local file |
Select this check box to append data to the specified local file |
|
Create directory if not exists |
Select this check box to create the directory specified in the |
S3 Setting |
Access Key |
Specify the Access Key ID that uniquely identifies an AWS Account. |
|
Secret Key |
Specify the Secret Access Key, constituting the security To enter the secret key, click the […] button next to |
|
Bucket |
Type in the name of the Amazon S3 bucket to which the file is |
|
Key |
Type in an object key to assign to the file uploaded to Amazon |
Advanced settings |
Fields terminated by |
Enter the character used to separate fields. |
|
Enclosed by |
Select the character in a pair of which the fields are |
|
Compressed by |
Select this check box and select a compression type from the list This field disappears when the Append the |
|
Encoding |
Select an encoding type for the data in the file to be |
|
Delete local file after putting it to s3 |
Select this check box to delete the local file after being |
|
Date format |
Select one of the following items from the list to specify the
|
|
Time format |
Select one of the following items from the list to specify the
|
|
Settings |
Click the [+] button below the
For more information about the parameters, see http://docs.aws.amazon.com/redshift/latest/dg/r_COPY.html. |
S3 Setting |
Config client |
Select this check box to configure client parameters for Amazon S3. Click the [+] button below the table displayed to
|
|
tStatCatcher Statistics |
Select this check box to gather the Job processing metadata at the |
Dynamic settings |
Click the [+] button to add a row in the table and fill The Dynamic settings table is available only when the For more information on Dynamic settings and context |
|
Global Variables |
ERROR_MESSAGE: the error message generated by the A Flow variable functions during the execution of a component while an After variable To fill up a field or expression with a variable, press Ctrl + For further information about variables, see Talend Studio |
|
Usage |
This component is mainly used when no particular transformation is required on the data |
|
Log4j |
The activity of this component can be logged using the log4j feature. For more information on this feature, see Talend Studio User For more information on the log4j logging levels, see the Apache documentation at http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Level.html. |
For a related scenario, see Loading/unloading data from/to Amazon S3.