# tRedshiftOutputBulkExec Executes the Insert action on the data provided. As a dedicated component, it allows gains in performance during Insert operations to Amazon Redshift. 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. This component receives data from the preceding component, generates a single delimited/CSV file and uploads the file to Amazon S3, finally it loads the data from Amazon S3 to Redshift. ## tRedshiftOutputBulkExec Standard properties These properties are used to configure tRedshiftOutputBulkExec running in the Standard Job framework. The Standard tRedshiftOutputBulkExec component belongs to the Cloud and the Databases families. The component in this framework is available in all Talend products. Information noteNote: This component is a specific version of a dynamic database connector. The properties related to database settings vary depending on your database type selection. For more information about dynamic database connectors, see [DB Generic components](https://help.qlik.com/talend/r/en-US/8.0/components/db-generic/db-generic-component). ## Basic settings | Properties | Description | | --- | --- | | Database | Select the desired database type from the list and click
Apply. | | Property Type | Either Built-In or
Repository.

| | Use an existing connection | Select this check box and in the Component
List drop-down list, select the desired connection component to
reuse the connection details you already defined. | | Driver version | Select the Redshift driver version to be used: Driver v1 or
Driver v2.

Information noteNote: This option is available only when you have installed the 8.0.1-R2022-04
Talend Studio
Monthly update or a later one delivered by Talend. For more information, check with your administrator. | | 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, enter the password in double quotes in the pop-up dialog box,
and click OK to save the settings. | | Use String JDBC parameters | Set JDBC properties in a string. If you select this option, enter your JDBC parameter string in
the Additional JDBC Parameters field; otherwise, enter JDBC
properties and property values in the Additional JDBC
Parameters table.

This option is not available if Driver v1 is selected from
the Driver version drop-down list.

Information noteNote: This option is available only when you have installed the 8.0.1-R2022-04
Talend Studio
Monthly update or a later one delivered by Talend. For more information, check with your administrator. | | 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.

This field is not available if Driver v2 is selected
from the Driver version drop-down list and the
Use String JDBC parameters option is not
selected. | | Additional JDBC Parameters (table) | Specify JDBC properties in table rows.

To specify a JDBC property, add a row in the table by clicking the plus button on
the bottom of this table, enter the property name in the
Key column, and then enter the property value in the
Value column.

This table is available when Driver v2 is selected from the
Driver version drop-down list and the Use
String JDBC parameters option is not selected.

Information noteNote: This option is available only when you have installed the 8.0.1-R2022-04
Talend Studio
Monthly update or a later one delivered by Talend. For more information, check with your administrator. | | 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:

| | 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:

| | 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
Talend Studio is installed or where the Job using this component is deployed. | | Append the local file | Select this check box to append data to the specified
local file if it already exists, instead of overwriting it. | | Create directory if not exists | Select this check box to create the directory specified
in the Data file path at local
field if it does not exist. By default, this check box is selected. | | Use an existing S3 connection | Select this check box and in the Component
List drop-down list, select the desired connection component to
reuse the connection details you already defined.

Information noteNote: This component works with static credentials only. That is, it does not
inherit credentials from AWS role. The component will generate an error in Job
execution if any option other than Static Credentials is
selected from the Credential Provider drop-down list of
the tS3Connection component that creates the S3 connection. | | Credential provider | Specify the way to obtain AWS security credentials: Static
credentials, which uses access key and
secret key as the AWS security credentials.

Information noteNote: This component works with static credentials only. That is, it does not
inherit credentials from AWS role. The component will generate an error in Job
execution if you select the Inherit credentials from AWS
role option. | | Access Key | Specify the Access Key ID that uniquely identifies an AWS
Account. For how to get your Access Key and Access Secret, visit [Getting Your AWS Access
Keys](http://docs.aws.amazon.com/ses/latest/DeveloperGuide/get-aws-keys.html).

Information noteNote: This option is available when Use an existing S3
connection is not selected or Inherit credentials from AWS
role is not selected from the Credential provider
drop-down list. | | 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.

Information noteNote: This option is available when Use an existing S3
connection is not selected or Inherit credentials from AWS
role is not selected from the Credential provider
drop-down list. | | S3 Assume Role | If you temporarily need some access permissions associated to an AWS IAM
role that is not granted to your user account, select this checkbox to assume that
role. Then specify the values for the following parameters to create a new assumed
role session.

Ensure that access to this
role has been granted to your user account by the trust policy associated to
this role. If you are not certain about this, ask the owner of this role or
your AWS administrator.

Information noteNote: This option is available
when Use an existing S3 connection is not
selected.




For an example about an IAM role and its related policy types, see [Create and Manage AWS IAM Roles](https://aws.amazon.com/blogs/security/now-create-and-manage-aws-iam-roles-more-easily-with-the-updated-iam-console/) from the AWS
documentation. | | Region | Specify the AWS region by selecting or entering a region name between double
quotation marks (e.g. *"us-east-1"*). For more information about the
AWS Region, see [Regions and Endpoints](http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region).

Information noteNote: This field
is available when Use an existing S3 connection
is not selected. | | Bucket | Type in the name of the Amazon S3 bucket, namely the top
level folder, to which the file is uploaded.

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](https://docs.aws.amazon.com/redshift/latest/dg/s3serviceexception-error.html). | | Key | Type in an object key to assign to the file uploaded to
Amazon S3. | | Redshift Assume Role | Select this checkbox and specify the values for the
following parameters used to create a new assumed role session.



For more information on IAM
Role ARNs chains, see [Authorizing Redshift service](https://docs.aws.amazon.com/redshift/latest/mgmt/authorizing-redshift-service.html). | ## Advanced settings | Properties | Description | | --- | --- | | Fields terminated by | Enter the character used to separate
fields. | | Enclosed by | Select the character in a pair of which
the fields are enclosed. | | Compressed by | Select this check box and select a
compression type from the list displayed to compress the data file.

This field disappears when the
Append the local
file check box is selected. | | Encrypt | Select this check box to generate and
upload the data file to Amazon S3 using 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](http://docs.aws.amazon.com/redshift/latest/dg/c_loading-encrypted-files.html).

By default, this check box is cleared
and the data file will be uploaded to Amazon S3 using server-side
encryption.

For more information about the
client-side and server-side encryption, see [Protecting Data
Using Encryption](http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingEncryption.html).

Information noteNote: This field is available when Use an existing S3 connection is not
selected. | | Encoding | Select an encoding type for the data in
the file to be generated. | | Delete local file after putting it to s3 | Select this check box to delete the
local file after being uploaded to Amazon S3. By default, this check box
is selected. | | Date format | Select one of the following items from
the list to specify the date format in the source data:

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

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



For more information about the
parameters, see http://docs.aws.amazon.com/redshift/latest/dg/r\_COPY.html. | | Config client | Select this check box to configure
client parameters for Amazon S3. Click the [+] button below the table displayed to
add as many rows as needed, each row for a client parameter, and set the
following attributes for each parameter:



For information about S3 client parameters, go to [Client Configuration](https://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/section-client-configuration.html). | | STS Endpoint | Select this check box to specify the AWS Security
Token Service (STS) endpoint from which to retrieve the session credentials.
For example, enter sts.amazonaws.com.

This check box is available only when the S3 Assume Role check box is
selected. | | Signing
region | Select the AWS region of the STS service. If the region
is not in the list, you can enter its name between double quotation
marks. The default value is us-east-1.

This drop-down list is available only when the
S3 Assume Role check box is
selected. | | External
Id | If the administrator of the account to which the role
belongs provided you with an external ID, enter its value here. The
External Id is a unique
identifier that allows a limited set of users to assume the role.

This field is available only when the S3 Assume Role check box is
selected. | | Serial
number | When you assume a role, the trust policy of this role
might require Multi-Factor Authentication (MFA). In this case, you must
indicate the identification number of the hardware or virtual MFA device
that is associated with the user who assumes the role.

This field is available only when the S3 Assume Role check box is
selected. | | Token
code | When you assume a role, the trust policy of this role
might require Multi-Factor Authentication (MFA). In this case, you must
indicate a token code. This token code is a time-based one-time password
produced by the MFA device.

This field is available only when the S3 Assume Role check box is
selected. | | Tags | List session tags in the form of key-value pairs. You
can then use these session tags in policies to allow or deny access to
requests.


Transitive:
select this check box to indicate that a tag will persist to the next
role in a role chain.

For more information about tags, see [Passing Session Tags in AWS
STS](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_session-tags.html#id_session-tags_role-chaining)

This field is available only when the S3 Assume Role check box is
selected. | | IAM Policy
ARNs | Enter the Amazon Resource Names (ARNs) of the IAM
managed policies that you want to use as managed session policies. Use
managed session policies to limit the permissions of the session. The
policies must exist in the same account as the role. The resulting
session's permissions are the intersection of the role's identity-based
policy and the session policies.

For more information about session policies, see the
corresponding section in [Policies and
Permissions](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session)

This field is available only when the S3 Assume Role check box is
selected. | | Policy | Enter an IAM policy in JSON format that you want to use
as a session policy. Use session policies to limit the permissions of
the session. The resulting session's permissions are the intersection of
the role's identity-based policy and the session policies.

For more information about session policies, see the
corresponding section in [Policies and
Permissions](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session)

This field is available only when the S3 Assume Role check box is
selected. | | JDBC
url | Select a way to access to an Amazon Redshift database from the
JDBC url drop-down list.

| | 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 | Variables | Description | | --- | --- | | 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 checkbox is
cleared, if the component has this checkbox.

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 more information about variables, see [Using contexts and variables](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/contexts-and-variables). | ## Usage | Usage guidance | Description | | --- | --- | | **Usage rule** | This component is mainly used when no
particular transformation is required on the data to be loaded to Amazon
Redshift. | | 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](https://help.qlik.com/talend/r/en-US/8.0/components/defining-context-groups/reading-data-from-databases-through-context-based-dynamic-connections) and [Reading data from different MySQL databases
using dynamically loaded connection parameters](https://help.qlik.com/talend/r/en-US/8.0/components/context/reading-data-from-different-mysql-databases-using-dynamically-loaded-connection-parameters). For more information on
Dynamic settings and context variables, see
[Dynamic schema](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/dynamic-schema) and [Creating a context group and define context
variables in it](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/creating-context-group-and-define-context-variables-in-it). |