Function |
tEXAOutput writes, updates, modifies or deletes data in an EXASolution database. | |
Purpose |
tEXAOutput executes the action defined on the table and/or on the data in the table, based on the flow incoming from the preceding component. |
Component family |
Databases/EXASolution |
| |
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. | |
|
|
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. NoteWhen 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 Talend Studio User Guide. | |
|
Host |
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, 172.16.173.128), an IP range list (for example, 172.16.173.128..130 that represents three servers 172.16.173.128, 172.16.173.129, and 172.16.173.130), or a comma-separated host list (for example, server1,server2,server3) of the EXASolution database 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 password field, and then in the pop-up dialog box enter the password between double quotes and click OK to save the settings. | |
|
Table |
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:
| |
|
Action on data |
On the data of the table defined, you can perform:
WarningYou 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 Schema 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. 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. 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. For more details, see the article Verifying default values in a retrieved schema on | |
|
|
Click Edit schema to make changes to the schema. If the current schema is of the Repository type, three options are available:
| |
|
Die on error |
Select this check box to stop the execution of the Job when an error occurs. 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 every 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 connection 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.
| |
|
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 data.
| |
|
Enable debug mode |
Select this check box to display each step of the process by which the data is written in the 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. | |
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 Scenario 3: Reading data from MySQL databases through context-based dynamic connections and Scenario: 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. | ||
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 + 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 |
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 Scenario 3: Retrieve data in error with a Reject link. | ||
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. | ||
Limitation |
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. For details, see the article Installing External Modules on Talend Help Center (https://help.talend.com) how to configure the Studio in the Talend Installation and Upgrade Guide. |
For similar scenarios using other databases, see: