tMemSQLRow
Acts on the actual database structure or on the data (although without handling
data).
tMemSQLRow executes the MemSQL query stated in the
specified database, depending on the nature of the query and the database. The row suffix
means the component implements a flow in the Job design although it does not provide output.
tMemSQLRow Standard properties
These properties are used to configure tMemSQLRow running in the Standard Job framework.
The Standard
tMemSQLRow component belongs to the Big Data and the Databases families.
The component in this framework is available when you are using one of the Talend solutions with Big Data.
Basic settings
|
Property type |
Either Built-in or |
|
|
Built-in: No property data stored |
|
|
Repository: Select the repository |
|
Use an existing connection |
Select this check box and in the Component 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 location of the server of the MemSQL database to be |
|
Port |
Enter the listening port number of the database server. |
|
Database |
Enter the name of the MemSQL database to be used. |
|
Username and |
Enter the user authentication data for connecting to the database |
|
Table Name |
Name of the table to be processed. |
|
Schema and Edit |
A schema is a row description. It defines the number of fields (columns) to |
|
|
Built-In: You create and store the |
|
|
Repository: You have already created When the schema to be reused has default values that are integers or You can find more details about how to verify default |
|
Click Edit schema to make changes to the schema.
|
|
|
Query type |
Either Built-in or |
|
|
Built-in: Fill in manually the |
|
|
Repository: Select the relevant query stored in the |
|
Guess |
Click the Guess Query button to |
|
Query |
Enter your DB query paying particularly attention to properly |
|
Die on error |
This check box is clear by default. This allows you to skip the |
Advanced settings
|
Additional JDBC parameters |
Specify additional connection properties for the database |
|
Propagate QUERY’s record set |
Select this check box to insert the result of the query in a Note:
This option allows the component to have a different schema |
|
Use PreparedStatement |
Select this check box if you want to query the database using a
Parameter Index: Enter the
Parameter Type: Enter the parameter
Parameter Value: Enter the Note:
This option is very useful if you need to execute the same |
|
tStatCatcher Statistics |
Select this check box to collect log data at the component |
Global Variables
|
Global Variables |
QUERY: the query statement being processed. This is a Flow
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 of the database query and |
|
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 scenarios
No scenario is available for the Standard version of this component yet.