
Warning
This component will be available in the Palette of
Talend Studio on the condition that you have subscribed to one of
the Talend
solutions with Big Data.
Component family |
Big Data/MemSQL |
|
Function |
This component opens a connection to the MemSQL database to be |
|
Purpose |
This component is used to open a connection to the specified database that can then be reused in the subsequent subjob or subjobs. |
|
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 |
|
Host |
Enter the location of the database server to be used. |
|
Port |
Enter the listening port number of the database server to be |
|
Database |
Enter the name of the database to be used. |
|
Username and |
DB user authentication data. |
|
Use or register a shared DB Connection |
Select this check box to share your connection or fetch a WarningThis option is incompatible with the Use dynamic job
Shared DB Connection Name: set or |
Advanced settings |
Additional JDBC parameters |
Specify additional connection properties for the DB connection you |
tStatCatcher Statistics |
Select this check box to gather the job processing metadata at a |
|
Global Variables |
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 more commonly used with other MemSQL |
|
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. |
|
Limitation |
Due to license incompatibility, one or more JARs required to use this component are not |
For a related scenario, see Scenario: Writing data to and reading data from a MemSQL database table.