Select a type of database 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.

File Name

Name of the file to be generated.

Append

Select this check box to append new rows to the end of the
file.

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

Repository: You have already created the schema and stored it in the
Repository. You can reuse it in various projects and Job designs.

When the schema to be reused has default values that are
integers or functions, ensure that these default values are not enclosed within
quotation marks. If they are, you must remove the quotation marks manually.

You can find more details about how to
verify default values in retrieved schema in Talend Help Center (https://help.talend.com).

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.

Row separator

String (ex: ”
“on Unix) to distinguish rows.

Field separator

Character, string or regular expression used to separate
fields

Set DBMONEY

Select this box if you want to define the decimal separator in the
corresponding field.

Set DBDATE

Select the date format that you want to apply.

Create directory if not exists

This check box is selected automatically. The option allows you to
create a folder for the output file if it doesn’t already
exist.

Custom the flush buffer size

Select this box in order to customize the memory size used to
store the data temporarily. In the Row
number field enter the number of rows at which point
the memory should be freed.

Encoding

Select the encoding from the list or select Custom and define it manually. This field is
compulsory for DB data handling.

tStatCatcher Statistics

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

Global Variables 

NB_LINE: the number of rows processed. This is an After
variable and it returns an integer.

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 +
Space 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 is generally used along with tInformixBulkExec. Together, they improve
performance levels when adding data to an Informix database.

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.

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
settings 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
Integration
perspective of your studio. You can find more details about how to install external modules in
Talend Help Center (https://help.talend.com).