July 30, 2023

tRedshiftRow – Docs for ESB 7.x


Acts on the actual DB structure or on the data (although without handling data),
depending on the nature of the query and the database.

The SQLBuilder tool helps you write easily your SQL statements.

tRedshiftRow is the specific
component for this database query. It executes the SQL query stated
onto the specified database. The row suffix means the component
implements a flow in the job design although it does not provide

tRedshiftRow Standard properties

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

The Standard
tRedshiftRow 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 Repository


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.

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.

Note: When a Job contains the parent Job and the child Job, if you
need to share an existing connection between the two levels, for example, to share the
connection created by the parent Job with the child Job, you have to:

  1. In the parent level, register the database connection
    to be shared in the Basic
    view of the connection component which creates that very database

  2. In the child level, use a dedicated connection
    component to read that registered database connection.

For an example about how to share a database connection
across Job levels, see

Talend Studio
User Guide


Hostname or IP address of the database server.


Listening port number of the database 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.


Exact name of the schema.

Username and Password

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

Schema and Edit

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


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


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

Table Name

Name of the table from which the data will be read.

Query type

Either Built-in or Repository


Built-in: Fill in manually the query
statement or build it graphically using SQLBuilder.


Repository: Select the relevant query
stored in the Repository. The Query
field gets accordingly filled in.

Guess Query

Click the Guess Query button to
generate the query which corresponds to your table schema in the Query


Enter your database query paying particularly attention to properly
sequence the fields in order to match the schema definition.

Note: All statements in this field will be executed in a single transaction. To
have multiple statements executed in different transactions, put each of them
in a separate tRedShiftRow component.

Die on error

This check box is selected by default. Clear the check box to skip the
row on error and complete the process for error-free rows. If needed,
you can retrieve the rows on error through a Row > Rejects

Advanced settings

Propagate QUERY’s recordset

Select this check box to insert the result of the query into a COLUMN
of the current flow. Select this column from the use column list.


This option allows the component to have a different schema from
that of the preceding component. Moreover, the column that holds the
QUERY’s recordset should be set to the type of Object and this component is usually
followed by tParseRecordSet.

Use PreparedStatement

Select this check box if you want to query the database using a
PreparedStatement. In the Set PreparedStatement
table, define the parameters represented by “?”
in the SQL instruction of the Query
field in the Basic Settings tab.

Parameter Index: Enter the parameter
position in the SQL instruction.

Parameter Type: Enter the parameter

Parameter Value: Enter the parameter


This option is very useful if you need to execute the same query
several times. Performance levels are increased.

Commit every

Number of rows to be completed before committing batches of rows
together into the database. This option ensures transaction quality (but
not rollback) and above all better performance on executions.

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.

Catcher Statistics

Select this check box to collect log data at the component

Global Variables

Global Variables

QUERY: the query statement being processed. This is a Flow
variable and it returns a string.

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

This component offers the flexibility benefit of the database query
and covers all possible SQL queries.

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
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
and context variables, see Talend Studio
User Guide.


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)

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