Skip to main content Skip to complementary content

tSingleStoreClose Standard properties

Availability-notesubscription

These properties are used to configure tSingleStoreClose running in the Standard Job framework.

The Standard tSingleStoreClose component belongs to the Databases family.

The component in this framework is available in all Talend products.

Information noteNote: This component is available only if you have installed the R2020-11 Studio Monthly update or a later one delivered by Talend. For more information, check with your administrator.

Basic settings

Database

Select a type of database from the list and click Apply.

Connection Component

Select the component that opens the connection you need to close from the drop-down list.

Advanced settings

tStatCatcher Statistics

Select this check box to gather the Job processing metadata at the Job level as well as at each component level.

Global Variables

ERROR_MESSAGE

The error message generated by the component when an error occurs. This is an After variable and it returns a string.

Usage

Usage rule

This component is to be used along with SingleStore components, especially with tSingleStoreConnection and tSingleStoreCommit.

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.

For examples on using dynamic parameters, see Reading data from databases through context-based dynamic connections and 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.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!