tEXAOutput
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 generally available.
Basic settings
Property Type |
Either Built-In or
|
Click this icon to open a database connection wizard and For more information about setting up and storing |
|
Use an existing connection |
Select this check box and from the list displayed select the relevant connection 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:
For an example about how to share a database connection across Job levels, see |
Host |
Enter the host or host list of the EXASol database servers. EXASol can run in a cluster |
Port |
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 |
Table |
Enter the name of the table to be written. Note that only |
Action on table |
On the table defined, you can perform one of the
|
Action on data |
On the data of the table defined, you can perform:
Warning:
You must specify at least one column as a primary key |
Schema and Edit schema |
A schema is a row description. It defines the number of fields (columns) to
Click Edit schema to make changes to the schema.
This component offers the This dynamic schema When the schema to be reused has default values that are integers or You can find more details about how to verify default |
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 |
Advanced settings
Use commit control |
Select this box to display the Commit |
Additional JDBC parameters |
Specify additional connection properties for the database connection you are This field is not available if the Use an existing |
Additional Columns |
This option is not offered if you create (with or without drop) the DB
|
Use field options |
Select this check box to customize a request for the corresponding
|
Enable debug mode |
Select this check box to display each step of the process by which the |
Use batch mode |
Select this check box to activate the batch mode for data processing, |
tStatCatcher Statistics |
Select this check box to gather the Job processing metadata at the Job level |
Global Variables
Global Variables |
NB_LINE: the number of rows processed. This is an After
NB_LINE_UPDATED: the number of rows updated. This is an
NB_LINE_INSERTED: the number of rows inserted. This is an
NB_LINE_DELETED: the number of rows deleted. This is an
NB_LINE_REJECTED: the number of rows rejected. This is an
ERROR_MESSAGE: the error message generated by the A Flow variable functions during the execution of a component while an After variable To fill up a field or expression with a variable, press Ctrl + For further information about variables, see |
Usage
Usage rule |
This component offers the flexibility benefit of the DB query and This component must be used as an output component. It allows you to |
Dynamic settings |
Click the [+] button to add a The Dynamic settings table is For examples on using dynamic parameters, see Scenario: Reading data from databases through context-based dynamic connections and Scenario: Reading data from different MySQL databases using dynamically loaded connection parameters. For more information on Dynamic |
Limitation |
Due to license incompatibility, one or more JARs required to use this component are not |
Related scenario
For similar scenarios using other databases, see: