tMysqlCDC Standard properties
These properties are used to configure tMysqlCDC running in the Standard Job framework.
The Standard tMysqlCDC component belongs to the Databases family.
The component in this framework is available in all Talend products.
Basic settings
Database |
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. Information noteWarning:
Reset the database type by clicking the relevant button to select the CDC connection. |
Use an existing connection |
Select this check box and in the Component List drop-down list, select the desired connection component to reuse the connection details you already defined. Information noteNote: 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 Talend Studio User Guide. |
Host |
Database server IP address. |
Port |
Database server listening port number. |
Database |
Name of the database. |
Username and Password |
Database 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. |
Schema using CDC and Edit Schema |
A schema is a row description, it defines the number of fields to be processed and passed on to the next component. The schema is either Built-in or stored remotely in the Repository. |
|
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. Information noteWarning:
Reset the database type by clicking the relevant button to select the schema of the CDC connection. |
Click Edit schema to make changes to the schema. If the current schema is of the Repository type, three options are available:
|
|
Table using CDC |
Select the source table from which changes made to data are to be captured. |
Subscriber |
Enter the name of the application that will use the change table. |
Events to catch |
Insert: Select this check box to catch the data inserted in the change table since the last extraction. Update: Select this check box to catch the data updated in the change table since the last extraction. Delete: Select this check box to catch the data deleted in the change table since the last extraction. |
Limit |
Maximum number of consumed rows a subscriber can recover from the change table, per execution. |
Advanced settings
Additional JDBC parameters |
Specify additional connection properties for the database connection you are creating. Not available when the Use an existing connection check box is selected. |
Keep data in CDC table | Select this check box to keep the changes made available to one or more target systems, even after they have been consulted. |
Enable Streaming Result | Select this check box to enables streaming over buffering which allows the code to read from a large table without consuming a large amount of memory in order to optimize the performance. |
Trim all the String/Char columns |
Select this check box to remove leading and trailing whitespace from all the String/Char columns. |
Trim column |
Remove leading and trailing whitespace from defined columns. Information noteNote:
Select Trim all the String/Char columns to enable Trim columns in this field. |
tStatCatcher Statistics |
Select this check box to collect log data at the component level. |
Enable parallel execution |
Select this check box to perform high-speed data processing, by treating
multiple data flows simultaneously. Note that this feature depends on the database or
the application ability to handle multiple inserts in parallel as well as the number of
CPU affected. In the Number of parallel executions
field, either:
Note that when parallel execution is enabled, it is not possible to use global variables to retrieve return values in a subJob.
|
Global Variables
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
Usage rule |
This component is used as a start component. It requires an output component and row Main link. |