Component family |
Cloud/AmazonRDS/Aurora |
|
Function |
This component reads an Amazon Aurora database and extracts fields |
|
Purpose |
This component executes a database query with a strictly defined |
|
Basic settings |
Property Type |
Either Built-In or Repository. Since version 5.6, both the Built-In mode and the Repository mode are |
|
|
Built-In: No property data stored |
|
|
Repository: Select the repository |
|
Use an existing connection |
Select this check box and in the Component List click the NoteWhen a Job contains the parent Job and the child Job, if you need to share an existing
For an example about how to share a database connection across Job levels, see |
|
Host |
Type in the IP address or hostname of the Amazon Aurora |
|
Port |
Type in the listening port number of the Amazon Aurora |
|
Database |
Type in the name of the database you want to use. |
|
Username and |
Type in the database user authentication data. To enter the password, click the […] button next to the |
|
Schema and Edit |
A schema is a row description. It defines the number of fields to be processed and passed on Since version 5.6, both the Built-In mode and the Repository mode are This component offers the advantage of the dynamic schema feature. This allows you to This dynamic schema feature is designed for the purpose of retrieving unknown columns |
|
|
Built-In: You create and store the schema locally for this |
|
|
Repository: You have already created the schema and |
|
|
Click Edit schema to make changes to the schema. If the
|
|
Table Name |
Type in the name of the table to be read. |
|
Query Type and Query |
Enter the database query paying particularly attention to the WarningIf using the dynamic schema feature, |
|
Guess Query |
Click the button to generate the query which corresponds to the |
|
Guess schema |
Click the button to retrieve the schema from the table. |
|
Specify a data source alias |
Select this check box and specify the alias of a data source created on the Talend Runtime side to use the shared connection pool defined in the data source configuration. This check box disappears when the Use an |
|
Data source alias |
Type in the alias of the data source created on the Talend Runtime side. This field appears only when the Specify a |
Advanced settings |
Additional JDBC parameters |
Specify additional connection properties for the database This field disappears when the Use an |
|
Enable stream |
Select this check box to enable streaming over buffering which |
|
Trim all the String/Char columns |
Select this check box to remove leading and trailing whitespace |
|
Trim column |
Select the check box(es) in the Trim column to remove leading and trailing This option disappears when the Trim all the |
|
tStatCatcher Statistics |
Select this check box to gather the Job processing metadata at the |
Dynamic settings |
Click the [+] button to add a row in the table and fill The Dynamic settings table is available only when the For more information on Dynamic settings and context |
|
Global Variables |
NB_LINE: the number of rows read by an input component or
QUERY: the SQL query statement being processed. This is a 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 Talend Studio |
|
Usage |
This component is usually used as a start component of a Job or |
|
Log4j |
The activity of this component can be logged using the log4j feature. For more information on this feature, see Talend Studio User 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. |
The Aurora database is compatible with MySQL v5.6. For similar scenarios, see: