tJDBCSCDELT Standard properties

SCDELT

author
Talend Documentation Team
EnrichVersion
6.5
EnrichProdName
Talend Data Integration
Talend Open Studio for Big Data
Talend Data Management Platform
Talend Real-Time Big Data Platform
Talend Data Services Platform
Talend Big Data
Talend ESB
Talend Open Studio for MDM
Talend Big Data Platform
Talend Data Fabric
Talend Open Studio for ESB
Talend MDM Platform
Talend Open Studio for Data Integration
task
Data Governance > Third-party systems > Business Intelligence components > SCDELT components
Data Quality and Preparation > Third-party systems > Business Intelligence components > SCDELT components
Design and Development > Third-party systems > Business Intelligence components > SCDELT components
EnrichPlatform
Talend Studio

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

The Standard tJDBCSCDELT component belongs to two families: Business Intelligence and Databases.

The component in this framework is generally available.

Basic settings

Property Type

Select the way the connection details will be set.

  • Built-In: The connection details will be set locally for this component. You need to specify the values for all related connection properties manually.

  • Repository: The connection details stored centrally in Repository > Metadata will be reused by this component. You need to click the [...] button next to it and in the pop-up Repository Content dialog box, select the connection details to be reused, and all related connection properties will be automatically filled in.

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.

JDBC URL

Specify the JDBC URL of the database to be used. For example, the JDBC URL for the Amazon Redshift database is jdbc:redshift://endpoint:port/database.

Driver JAR

Complete this table to load the driver JARs needed. To do this, click the [+] button under the table to add as many rows as needed, each row for a driver JAR, then select the cell and click the [...] button at the right side of the cell to open the Select Module wizard from which you can select the driver JAR of your interest. For example, the driver jar RedshiftJDBC41-1.1.13.1013.jar for the Redshift database.

Driver Class

Enter the class name for the specified driver between double quotation marks. For example, for the RedshiftJDBC41-1.1.13.1013.jar driver, the name to be entered is com.amazon.redshift.jdbc41.Driver.

Username and Password

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.

DB Schema

Specify the name of the database schema. For the database that does not support schema, just leave this field empty.

Source table

Specify the name of the source input table whose data changes will be captured by SCD.

Table

Specify the name of the dimension table into which the data captured by SCD will be written.

Action on table

Select an operation to be performed on the table defined.

  • 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 does not exist: The table is created if it does not exist.

  • Drop table if exist 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.

  • Truncate table: The table content is deleted. You do not 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 Repository. 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. Related topic: see Talend Studio User Guide.

  • Repository: You have already created the schema and stored it in the Repository. You can reuse it in various projects and Job designs. Related topic: see Talend Studio User Guide.

Click Edit schema to make changes to the schema. Note that if you make changes, the schema automatically becomes built-in.

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

Surrogate key

Set the column where the generated surrogate key will be stored. A surrogate key can be generated based on a method selected on the Creation list.

Creation

Select any of the following methods to be used for generating the surrogate key.

  • Auto increment: an auto-incrementing integer will be used.

  • DB sequence: a sequence will be used.

Source keys

Specify one or more columns used as the key(s) that ensure the unicity of the incoming data.

Use SCD type 1 fields

Select this check box and in the SCD type 1 fields table displayed, specify the column(s) whose value changes will be tracked using Type 1 SCD.

SCD type 1 fields

Click the [+] button to add as many rows as needed, each row for a column, then click the right side of the cell and from the drop-down list displayed select the colulmn whose value changes will be tracked using Type 1 SCD.

Use SCD type 2 fields

Select this check box and in the SCD type 2 fields table displayed, specify the column(s) whose value changes will be tracked using Type 2 SCD.

SCD type 2 fields

Click the [+] button to add as many rows as needed, each row for a column, then click the right side of the cell and from the drop-down list displayed select the column whose value changes will be tracked using Type 2 SCD.

Start date

Specify the column that holds the start date for type 2 SCD.

End date

Specify the column that holds the end date for type 2 SCD.

Log active status

Select this check box and from the Active field drop-down list displayed, select the column that holds the true or false status value, which helps to spot the active record for type 2 SCD.

Log versions

Select this check box and from the Version field drop-down list displayed, select the column that holds the version number of the record for type 2 SCD.

Mapping

Specify the metadata mapping file for the database to be used. The metadata mapping file is used for the data type conversion between database and Java. For more information about the metadata mapping, see the related documentation for Type mapping.

Advanced settings

Source fields value include Null

Select this check box to allow the source columns to have Null values. The source columns here refer to the fields defined in the SCD type 1 fields and SCD type 2 fields tables.

Debug mode

Select this check box to display each step during processing the data in a database.

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.

Usage

Usage rule

This component can be used as a standalone component of a Job or Subjob.