tRedshiftConnection Standard properties - Cloud - 8.0

Select the desired database type 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 in which the properties are stored. The fields that follow are completed automatically using the data retrieved.

Driver version

Select the Redshift driver version to be used: Driver v1 or Driver v2.

Host

Host name or IP address of DB server.

Port

Listening port number of DB server.

Database

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.

Schema

Name of the schema.

Username and Password

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

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.

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.

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

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 tRedshiftRollback components.

Limitation

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 Integration perspective of Talend Studio. For details, see Installing external modules.