tPostgresPlusClose

Closes the transaction committed in the connected PostgresPlus
database.

tPostgresPlusClose Standard properties

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

The Standard
tPostgresPlusClose component belongs to the Databases family.

The component in this framework is generally available.

Basic settings

Component list	Select the tPostgresPlusConnection component in the list if more than one connection are planned for the current Job.

Advanced settings

tStat Catcher Statistics	Select this check box to collect log data at the component level.
Enable parallel execution	Select this check box to perform high-speed data processing, by treating multiple data flows simultaneously. Note that this feature depends on the database or the application ability to handle multiple inserts in parallel as well as the number of CPU affected. In the Number of parallel executions field, either: Enter the number of parallel executions desired. Press Ctrl + Space and select the appropriate context variable from the list. For further information, see Talend Studio User Guide. Note that when parallel execution is enabled, it is not possible to use global variables to retrieve return values in a subjob. The Action on table field is not available with the parallelization function. Therefore, you must use a tCreateTable component if you want to create a table. When parallel execution is enabled, it is not possible to use global variables to retrieve return values in a subjob.

tStat
Catcher
Statistics

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

Enable parallel execution

Select this check box to perform high-speed data processing, by treating multiple data flows
simultaneously. Note that this feature depends on the database or the application ability to
handle multiple inserts in parallel as well as the number of CPU affected. In the Number of parallel executions field, either:

Enter the number of parallel executions desired.
Press Ctrl + Space and select the appropriate
context variable from the list. For further information, see
Talend Studio
User Guide.

Note that when parallel execution is enabled, it is not possible to use global variables to
retrieve return values in a subjob.

The Action on table
field is not available with the parallelization function. Therefore, you
must use a tCreateTable component if you
want to create a table.
When parallel execution is enabled, it is not possible to use global
variables to retrieve return values in a subjob.

Usage

Usage rule	This component is to be used along with PostgresPlus components, especially with tPostgresPlusConnection and tPostgresPlusCommit.
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.

Usage rule

This component is to be used along with PostgresPlus components,
especially with tPostgresPlusConnection and tPostgresPlusCommit.

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.

Related scenarios

No scenario is available for the Standard version of this component yet.

Document get from Talend https://help.talend.com

Thank you for watching.

Docs 6.x

0 Comments

Inline Feedbacks

View all comments

tPostgresPlusClose – Docs for ESB 6.x

tPostgresPlusClose