tTeradataFastLoadUtility Properties - 6.3

Talend Open Studio for Big Data Components Reference Guide

EnrichVersion
6.3
EnrichProdName
Talend Open Studio for Big Data
task
Data Governance
Data Quality and Preparation
Design and Development
EnrichPlatform
Talend Studio

Component Family

Databases/Teradata

 

Basic settings

Property type

Either Built-in or Repository.

Since version 5.6, both the Built-In mode and the Repository mode are available in any of the Talend solutions.

 

 

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.

 

Execution platform

Select the Operating System type you use.

 

Host

Host name or IP address of the database server.

 

Database name

Database name.

 

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.

 

Table

Name of the table to be written. Note that only one table can be written at a time.

 

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. The schema is either Built-In or stored remotely in the Repository.

Since version 5.6, both the Built-In mode and the Repository mode are available in any of the Talend solutions.

 

 

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. 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] window.

 

Script generated folder

Browse your directory and select the destination of the file which will be created.

 

Load file

Browse your directory and select the file from which you want to load data.

 

Field separator

Character, string or regular expression to separate fields.

 

Error file

Browse your directory and select the destination of the file where the error messages will be recorded.

Advanced settings

Define character set

Specify the character encoding you need use for your system.

 

Check point

Enter the check point value.

 

Error files

Enter the file name where the error messages are stored. By default, the code ERRORFILES table_ERR1, table_ERR2 is entered, meaning that the two tables table_ERR1 and table_ERR2 are used to record the error messages.

 

Return fastload error

Select this check box to specify the exit code number to indicate the point at which an error message should display in the console.

 

ERRLIMIT

Enter the limit number of errors detected during the loading phase. Processing stops when the limit is reached.

The default error limit value is 1000000.

For more information, see Teradata FastLoad Reference documentation.

 

tStatCatcher Statistics

Select this check box to collect log data at the component level.

Usage

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

Log4j

If you are using a subscription-based version of the Studio, the activity of this component can be logged using the log4j feature. For more information on this feature, see Talend Studio User Guide.

For more information on the log4j logging levels, see the Apache documentation at http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Level.html.