July 30, 2023

tEXAOutput – Docs for ESB 7.x


Writes, updates, modifies or deletes data in an EXASolution database by executing the
action defined on the table and/or on the data in the table, based on the flow incoming from
the preceding component.

tEXAOutput Standard properties

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

The Standard
tEXAOutput component belongs to the Databases family.

The component in this framework is available in all Talend

Note: This component is a specific version of a dynamic database
connector. The properties related to database settings vary depending on your database
type selection. For more information about dynamic database connectors, see Dynamic database components.

Basic settings


Select a type of database from the list and click

Property Type

Either Built-In or

  • Built-In: No property data
    stored centrally.

  • Repository: Select the
    repository file in which the properties are stored. The database
    connection fields that follow are completed automatically using
    the data retrieved.


Click this icon to open a database connection wizard and
store the database connection parameters you set in the component
Basic settings view.

For more information about setting up and storing
database connection parameters, see
Talend Studio User Guide

Use an existing connection

Select this check box and from the list displayed select the
relevant connection component to reuse the connection details you have already defined.

Note: When a Job contains the parent Job and the child Job, if you
need to share an existing connection between the two levels, for example, to share the
connection created by the parent Job with the child Job, you have to:

  1. In the parent level, register the database connection
    to be shared in the Basic
    view of the connection component which creates that very database

  2. In the child level, use a dedicated connection
    component to read that registered database connection.

For an example about how to share a database connection
across Job levels, see

Talend Studio
User Guide


Enter the host or host list of the EXASol database servers. EXASol can run in a cluster
environment. The valid value can be a simple IP address (for example,, an IP range list (for example, that represents three servers,, and, or a
comma-separated host list (for example, server1,server2,server3) of the EXASolution database cluster.


Enter the listening port number of the EXASolution database cluster.

Schema name

Enter the name of the schema you want to use.

Username and Password

Enter the user authentication data to access the EXASolution database.

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.


Enter the 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 does not
    : The table is created if it does not

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

  • Clear table: The table
    content is deleted.

  • Truncate table: The table
    content is deleted. You don not have the possibility to rollback
    the operation.

Action on data

On the data of the table defined, you can perform:

  • Insert: Add new entries
    to the table. If duplicates are found, Job stops.

  • Update: Make changes to
    existing entries

  • Insert or update: Insert a new record. If
    the record with the given reference already exists, an update would be made.

  • Update or insert: Update the record with the
    given reference. If the record does not exist, a new record would be inserted.

  • Delete: Remove entries
    corresponding to the input flow.


You must specify at least one column as a primary key
on which the Update and
Delete operations are
based. You can do that by clicking Edit
and selecting the check box(es) next to the
column(s) you want to set as primary key(s). For an advanced use,
click the Advanced settings
view where you can simultaneously define primary keys for the update
and delete operations. To do that: Select the Use field options check box and then
in the Key in update column,
select the check boxes next to the column name on which you want to
base the update operation. Do the same in the Key in delete column for the
deletion operation.

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

  • Built-In: You create and store the schema locally for this component

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

Click Edit
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

component offers the advantage of the dynamic schema feature. This allows you to
retrieve unknown columns from source files or to copy batches of columns from a source
without mapping each column individually. For further information about dynamic schemas,
Talend Studio

User Guide.

dynamic schema feature is designed for the purpose of retrieving unknown columns of a
table and is recommended to be used for this purpose only; it is not recommended for the
use of creating tables.

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

Die on error

Select the check box to stop the execution of the Job when an error

Clear the check box to skip any rows on error and complete the process for
error-free rows. When errors are skipped, you can collect the rows on error using a Row > Reject link.

Advanced settings

Use commit control

Select this box to display the Commit
field in which you can define the number of rows to
be processed before committing.

Additional JDBC parameters

Specify additional connection properties for the database connection you are
creating. The properties are separated by semicolon and each property is a key-value
pair, for example, encryption=1;clientname=Talend.

This field is not available if the Use an existing
check box is selected.

Additional Columns

This option is not offered if you create (with or without drop) the DB
table. This option allows you to call SQL functions to perform actions
on columns, which are not insert, nor update or delete actions, or
action that require particular preprocessing.

  • Name: Enter the name of the
    column to be modified or inserted.

  • SQL expression: Enter the SQL
    expression to be executed to modify or insert data in the
    corresponding columns.

  • Position: Select Before, After or Replace, depending on the action to be carried
    out on the reference column.

  • Reference column: Type in a
    column of reference that can be used to place or replace the new
    or altered column.

Use field options

Select this check box to customize a request for the corresponding
column, particularly if multiple actions are being carried out on the

  • Key in update: Select the
    check box for the corresponding column based on which the data
    is updated.

  • Key in delete: Select the
    check box for the corresponding column based on which the data
    is deleted.

  • Updatable: Select the check
    box if the data in the corresponding column can be

  • Insertable: Select the check
    box if the data in the corresponding column can be

Debug query mode

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

Use batch mode

Select this check box to activate the batch mode for data processing,
and in the Batch Size field displayed
enter the number of records to be processed in each batch.

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

Global Variables 

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

NB_LINE_UPDATED: the number of rows updated. This is an
After variable and it returns an integer.

NB_LINE_INSERTED: the number of rows inserted. This is an
After variable and it returns an integer.

NB_LINE_DELETED: the number of rows deleted. This is an
After variable and it returns an integer.

NB_LINE_REJECTED: the number of rows rejected. 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 +
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 offers the flexibility benefit of the DB query and
covers all of the SQL queries possible.

This component must be used as an output component. It allows you to
carry out actions on a table or on the data of a table in an EXASolution
database. It also allows you to create a reject flow using a Row > Rejects link to filter data in
error. For a related scenario, 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
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
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
perspective of your studio. You can find more details about how to install external modules in
Talend Help Center (https://help.talend.com)

Related scenario

For similar scenarios using other databases, see:

Document get from Talend https://help.talend.com
Thank you for watching.
Notify of
Inline Feedbacks
View all comments
Would love your thoughts, please comment.x