July 30, 2023

tRedshiftConnection – Docs for ESB 7.x


Opens a connection to the specified database that can then be reused in the
subsequent subjob or subjobs.

tRedshiftConnection opens a
connection to the database for a current transaction.

tRedshiftConnection Standard properties

These properties are used to configure tRedshiftConnection running in the Standard Job framework.

The Standard
tRedshiftConnection component belongs to the Cloud and the Databases families.

The component in this framework is available in all Talend

Note: 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 Dynamic database components.

Basic settings


Select a type of database from the list and click

Property type

Either Built-in or


Built-in: No property data stored


Repository: Select the repository file
in which the properties are stored. The fields that follow are completed
automatically using the data retrieved.


Host name or IP address of DB server.


Listening port number of DB server.


Name of the database.

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.


Name of the schema.

Username and Password

DB 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 &
, which means the
connection will be created using SSL.

Use or register a shared DB Connection

Select this check box to share your
database connection or fetch a database connection shared by a parent or child Job,
and in the Shared DB Connection Name field displayed, enter the
name for the shared database connection. This allows you to share one single database
connection (except the database schema setting) among several database connection
components from different Job levels that can be either parent or child.

This option is
incompatible with the Use dynamic job and Use an
independent process to run subjob
options of the
tRunJob component. Using a shared connection together with a
tRunJob component with either of these two options enabled
will cause your Job to fail.

Advanced settings

Log file

Specify the path to the log file to be generated during the
data retrieval process.

Note that if the logging information needs to be saved and
this component reuses the connection created by a tRedshiftConnection component, you must specify the property loglevel=1/2/3 in the Additional JDBC Parameters
field of the tRedshiftConnection component.

There is no limitation on the size of the log file. If the
specificed log file already exists, it will be overwritten.

Logging level

Select a logging level from the drop-down list to specify
which kind of events will be logged in the log file.

Auto Commit

Select this check box to commit any changes to the database
automatically upon the transaction.

With this check box selected, you cannot use the corresponding
commit component to commit changes to the database; likewise, when using the
corresponding commit component, this check box has to be cleared. By
default, the auto commit function is disabled and changes must be committed
explicitly using the corresponding commit component.

Note that the auto commit function commits each SQL statement as a
single transaction immediately after the statement is executed while the
commit component does not commit only until all of the statements are
executed. For this reason, if you need more room to manage your transactions
in a Job, it is recommended to use the commit component.

JDBC url
Select a way to access to an Amazon Redshift database from the
JDBC url drop-down list.

  • Standard: Use the
    standard way to access the Redshift database.
  • SSO: Use the IAM
    Single Sign-ON (SSO) authentication way to access the Redshift Database. Before selecting
    this option, ensure that the IAM role added to your Redshift cluster has appropriate
    access rights and permissions to this cluster. You can ask the administrator of your AWS
    services for more details.

    This option is available only when Use an existing connection check box is not selected from
    the Basic settings.

tStatCatcher Statistics

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


Usage rule

This component is more commonly used with other tRedshift* components,
especially with the tRedshiftCommit and


Due to license incompatibility, one or more JARs required to use
this component are not provided. You can install the missing JARs for this particular
component by clicking the Install button
on the Component tab view. You can also
find out and add all missing JARs easily on the Modules tab in the
perspective of your studio. You can find more details about how to install external modules in
Talend Help Center (https://help.talend.com)

Related scenario

For a related scenario, see Handling data with Redshift.

Document get from Talend https://help.talend.com
Thank you for watching.
Notify of
Inline Feedbacks
View all comments
Would love your thoughts, please comment.x