tVerticaRollback Standard properties

Vertica

author
Talend Documentation Team
EnrichVersion
6.4
EnrichProdName
Talend Open Studio for ESB
Talend Open Studio for MDM
Talend Data Integration
Talend MDM Platform
Talend Open Studio for Data Integration
Talend Real-Time Big Data Platform
Talend ESB
Talend Open Studio for Big Data
Talend Data Services Platform
Talend Data Fabric
Talend Big Data Platform
Talend Big Data
Talend Data Management Platform
task
Design and Development > Third-party systems > Database components > Vertica components
Data Governance > Third-party systems > Database components > Vertica components
Data Quality and Preparation > Third-party systems > Database components > Vertica components
EnrichPlatform
Talend Studio

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

The Standard tVerticaRollback component belongs to the Databases family.

The component in this framework is generally available.

Basic settings

Component list

Select the VerticaConnection component in the list if more than one connection are planned for the current job.

Close Connection

Clear this check box to continue to use the selected connection once the component has performed its task.

Advanced settings

tStatCatcher Statistics

Select this check box to collect log data at the component level.

Usage

Usage rule

This component is more commonly used with other tVertica* components, especially with the tVerticaConnection and tVerticaCommit components.

Used together, Talend Studio and the Vertica database create very fast and affordable data warehouse and data mart applications. For more information about how to configure Talend Studio to connect to Vertica, see Talend and HP Vertica Tips and Techniques.

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 .

Once a dynamic parameter is defined, the Component List box in the Basic settings view becomes unusable.

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 settings and context variables, see Talend Studio User Guide.