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.

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.

Host

Database server IP address.

Port

Listening port number of the DB server.

Database

Database name.

Schema

Exact name of the schema.

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

Action on table

On the table defined, you can perform one of the following
operations:

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

Drop table if exists and create:
The table is removed if already exists and created again.

Clear table: The table content is
deleted.

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.

Additional JDBC Parameters

Specify additional JDBC parameters for the
database connection created.

This property is not available when the Use an existing connection
check box in the Basic settings view is selected.

Copy mode

Select the copy mode you want to use from either:

Basic: Standard mode, without
optimisation.

Parallel: Allows you to use several
internal ParAccel APIs in order to optimise loading speed.

Filename

Name of the file to be loaded.

File Type

Select the file type from the list.

Field Layout

Select the field layout from the list.

Field separator

Character, string or regular expression to separate fields.

Explicit IDs

The ID is already present in the file to be loaded or will be set
by the database.

Remove Quotes

Select this check box to remove quotation marks from the file to
be loaded.

Max. Errors

Type in the maximum number of errors before your Job stops.

Date Format

Type in the date format to be used.

Time/Timestamp Format

Enter the date and hour format to be used.

Additional COPY Options

Enter the specific, customized ParAccel option that you want to
use.

Log file

Browse to or enter the access path to the log file in your
directory.

Logging level

Select the information type you want to record in your log
file.

tStat
Catcher Statistics

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

Usage rule

This component covers all possible SQL database queries. It allows
you to carry out actions on a table or on the data of a table in a
ParAccel database. It enables you to create a reject flow, with a
Row > Reject link filtering the data in error. For a usage
example, see Retrieving data in error with a Reject link.

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