Select a type of database from the list and click
Apply.

Property Type

Either Built-In or Repository.

• Built-In: No property data stored centrally.

• Repository: Select the repository file where the
  properties are stored.

Use an existing
connection

Select this check box and in the Component List click the relevant connection component to
reuse the connection details you already defined.

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
password field, and then in the pop-up dialog box enter the password between double quotes
and click OK to save the settings.

Additional JDBC
Parameters

Specify additional JDBC properties for the connection you are creating. The
properties are separated by ampersand & and each property is a key-value pair. For
example, ssl=true &
sslfactory=com.amazon.redshift.ssl.NonValidatingFactory, which means the
connection will be created using SSL.

Table Name

Specify the name of the table to be written.
Note that only one table can be written at a time.

Action on table

On the table defined, you can perform one of
the following operations:

• None: No operation
  is carried out.

• Drop and create
  table: The table is removed and created again.

• Create table: The
  table does not exist and gets created.

• Create table if not
  exists: The table is created if it does not exist.

• Drop table if exists and
  create: The table is removed if it already exists and
  created again.

• Clear table: The
  table content is deleted. You have the possibility to rollback the
  operation.

Schema and Edit schema

A schema is a row description. It defines the number of fields
(columns) to be processed and passed on to the next component. When you create a Spark
Job, avoid the reserved word line when naming the
fields.

• Built-In: You create and store the schema locally for this component
  only.

• Repository: You have already created the schema and stored it in the
  Repository. You can reuse it in various projects and Job designs.

Click Edit
schema to make changes to the schema. If the current schema is of the Repository type, three options are available:

• View schema: choose this
  option to view the schema only.

• Change to built-in property:
  choose this option to change the schema to Built-in for local changes.

• Update repository connection:
  choose this option to change the schema stored in the repository and decide whether
  to propagate the changes to all the Jobs upon completion. If you just want to
  propagate the changes to the current Job, you can select No upon completion and choose this schema metadata
  again in the Repository Content
  window.

Data source type

Select the location of the source data to be
loaded.

• S3: load data
  from a file in an Amazon S3 bucket.

• EMR: load data
  from an Amazon EMR cluster.

• DynamoDB: load
  data from an existing DynamoDB table.

• Remote host: load
  data from one or more remote hosts, such as Amazon Elastic Compute Cloud
  (Amazon EC2) instances or other computers.

For more information, see Data Sources.

Select this check box and in the Component List click the relevant connection component to
reuse the connection details you already defined.

This option is available when S3 is selected from the
Data source type drop-down list.

Access Key/S3 Access Key

Specify the Access Key ID that uniquely
identifies an AWS account. For how to get your Access Key and Access Secret
Key, visit Getting Your AWS Access
Keys.

Secret Key/S3 Secret Key

Specify the Secret Access Key, constituting
the security credentials in combination with the Access Key.

To enter the secret key, click the […] button next to
the secret key field, and then in the pop-up dialog box enter the password between double
quotes and click OK to save the settings.

Assume Role

Select this check box and specify the
values for the following parameters used to create a new assumed role session.

• IAM Role ARNs chains: a series of chained roles, which
  may belong to other accounts, that your cluster can assume to access resources.

  You
  can chain a maximum of 10 roles.

• Role ARN: the Amazon Resource Name (ARN) of the role
  to assume.

This option is not available if Use an existing S3
connection is selected.

For more information on IAM Role ARNs
chains, see Authorizing Redshift service.

Bucket/S3 bucket

Specify the name of the Amazon S3 bucket in
which the file is located.

This field is available only when S3 or Remote host is selected from
the Data source type
drop-down list.

The bucket and the Redshift database to be used
must be in the same region on Amazon. This could avoid the S3ServiceException errors known to
Amazon. For further information about these errors, see S3ServiceException Errors.

Key

Specify the path to the file that contains the
data to be loaded.

This field is available only when S3 is selected from the
Data source type
drop-down list.

Cluster id

Specify the ID of the cluster that stores the
data to be loaded.

This field is available only when EMR is selected from the
Data source type
drop-down list.

HDFS path

Specify the HDFS file path that references the
data file.

This field is available only when EMR is selected from the
Data source type
drop-down list.

Table

Specify the name of the DynamoDB table that
contains the data to be loaded.

This field is available only when DynamoDB is selected from the
Data source type
drop-down list.

Read ratio

Specify the percentage of the DynamoDB table’s
provisioned throughput to use for the data load.

This field is available only when DynamoDB is selected from the
Data source type
drop-down list.

SSH manifest file

Specify the object key for the SSH manifest
file that provides the information used to open SSH connections and execute
remote commands.

This field is available only when Remote host is selected from
the Data source type
drop-down list.

File type

Select the type of the file that contains the
data to be loaded.

• Delimited file or
  CSV: a delimited/CSV file.

• JSON: a JSON
  file.

• AVRO: an Avro
  file.

• Fixed width: a
  fixed-width file.

This list is available when S3, EMR, or Remote host is selected from the Data source type drop-down
list.

Fields terminated by

Enter the character used to separate
fields.

This field is available only when Delimited file or CSV is
selected from the File
type list.

Enclosed by

Select the character in which the fields are
enclosed.

This list is available only when Delimited file or CSV is
selected from the File
type list.

JSON mapping

Specify how to map the data elements in the
source file to the columns in the target table on Amazon Redshift. The valid
values are:

• auto: Map the
  data by matching object keys or names in the source name/value pairs for
  a JSON file or field names in the Avro schema for an Avro file to the
  names of columns in the target table. The argument is case-sensitive and
  must be enclosed in double quotation marks.

• s3://jsonpaths_file: Map the data
  using the named JSONPaths file. The parameter must be an Amazon S3 object
  key that is enclosed in double quotation marks and explicitly references
  a single file, for example, s3://mybucket/jsonpaths.txt. For more information, see Data Format
  Parameters.

This field is available only when JSON or AVRO is selected from the
File type list.

Fixed width mapping

Enter a string that specifies a user-defined
column label and column width between double quotation marks. The format of the
string is:

ColumnLabel1:ColumnWidth1,ColumnLabel2:ColumnWidth2,....

Note that the column label in the string has
no relation to the table column name and it can be either a text string or an
integer. The order of the label/width pairs must match the order of the table
columns exactly.

This field is available only when Fixed width is selected from
the File type
list.

Compressed by

Select this check box and from the list
displayed select the compression type of the source file.

This check box is available when S3, EMR, or Remote host is selected from
the Data source type
drop-down list.

Decrypt

Select this check box if the file is
encrypted using Amazon S3 client-side encryption. In the Encryption key field
displayed, specify the encryption key used to encrypt the file. Note that only
a base64 encoded AES 128-bit or AES 256-bit envelope key is supported. For more
information, see Loading Encrypted Data
Files from Amazon S3.

This check box is available when S3 is selected from the
Data source type
drop-down list and Use an existing S3 connection is not
selected in the Basic settings view.

Encoding

Select the encoding type of the data to be
loaded from the list.

This list is available when S3, EMR, or Remote host is selected from
the Data source type
drop-down list.

Date format

Select one of the following items from the
list to specify the date format in the source data:

• NONE: No date
  format is specified.

• PATTERN: Select
  this item and specify the date format in the field displayed. The default
  date format is YYYY-MM-DD.

• AUTO: Select
  this item if you want Amazon Redshift to recognize and convert
  automatically the date format.

Time format

Select one of the following items from the
list to specify the time format in the source data:

• NONE: No time
  format is specified.

• PATTERN: Select
  this item and specify the time format in the field displayed. The default
  time format is YYYY-MM-DD HH:MI:SS.

• AUTO: Select
  this item if you want Amazon Redshift to recognize and convert
  automatically the time format.

• EPOCHSECS:
  Select this item if the source data is represented as epoch time, the
  number of seconds since Jan 1, 1970 00:00:00 UTC.

• EPOCHMILLISECS:
  Select this item if the source data is represented as epoch time, the
  number of milliseconds since Jan 1, 1970 00:00:00 UTC.

Settings

Click the [+] button below the table to specify more
parameters for loading the data.

• Parameter: Click
  the cell and select a parameter from the drop-down list.

• Value: Set the
  value for the corresponding parameter. Note that you cannot set the value
  for a parameter (such as IGNOREBLANKLINES) that does not need a value.

For more information about the parameters,
see http://docs.aws.amazon.com/redshift/latest/dg/r_COPY.html.

tStatCatcher
Statistics

Select this check box to gather the Job processing metadata at the Job level
as well as at each component level.

Global Variables

ERROR_MESSAGE: the error message generated by the
component when an error occurs. This is an After variable and it returns a string. This
variable functions only if the Die on error check box is
cleared, if the component has this check box.

A Flow variable functions during the execution of a component while an After variable
functions after the execution of the component.

To fill up a field or expression with a variable, press Ctrl +
Space to access the variable list and choose the variable to use from it.

For further information about variables, see
Talend Studio

User Guide.

Usage rule

The tRedshiftBulkExec component supports loading
data to Amazon Redshift from a delimited/CSV, JSON, or fixed-width file on
Amazon S3, but the tRedshiftOutputBulk component now only supports generating and
uploading a delimited/CSV file to Amazon S3. When you need to load data from a
JSON or fixed-width file, you can use the tFileOutputJSON or tFileOutputPositional component together with
the tS3Put component
instead of using the tRedshiftOutputBulk component to generate and upload the file
to Amazon S3.

Dynamic settings

Click the [+] button to add a row in the table
and fill the Code field with a context
variable to choose your database connection dynamically from multiple
connections planned in your Job. This feature is useful when you need to
access database tables having the same data structure but in different
databases, especially when you are working in an environment where you
cannot change your Job settings, for example, when your Job has to be
deployed and executed independent of Talend Studio.

The Dynamic settings table is
available only when the Use an existing
connection check box is selected in the Basic settings view. Once a dynamic parameter is
defined, the Component List box in the
Basic settings view becomes unusable.

For examples on using dynamic parameters, see Reading data from databases through context-based dynamic connections and Reading data from different MySQL databases using dynamically loaded connection parameters. For more information on Dynamic
settings and context variables, see Talend Studio
User Guide.