|
Component family
|
Databases/PostgresPlus
|
|
|
Function
|
Validates the data processed through the Job into the connected
DB.
|
|
Purpose
|
Using a unique connection, this component commits in one go a
global transaction instead of doing that on every row or every batch
and thus provides gain in performance.
Note that if you need to commit each statement as an individual transaction, you have to use
the Auto Commit function available in the connection
component.
|
|
Basic settings
|
Component list
|
Select the tPostgresPlusConnection component in the list if
more than one connection are planned for the current Job.
|
|
|
Close Connection
|
This check box is selected by default. It allows you to close the
database connection once the commit is done. Clear this check box to
continue to use the selected connection once the component has
performed its task.
Warning
If you want to use a Row >
Main
connection to link tPostgresPlusCommit to your Job, your data
will be committed row by row. In this case, do not select
the Close connection check
box or your connection will be closed before the end of your
first row commit.
|
|
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.
Warning
-
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.
|
|
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 more information on Dynamic settings and context
variables, see Talend Studio User Guide.
|
|
Usage
|
This component is more commonly used with other tPostgresPlus* components, especially
with the tPostgresPlusConnection
and tPostgresPlusRollback
components.
|
|
Log4j
|
The activity of this component can be logged using the log4j feature. For more information on this feature, see Talend Studio User
Guide.
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
|
n/a
|
