|
Component family
|
Databases/Vertica
|
|
|
Function
|
tVerticaOutput writes, updates,
makes changes or suppresses entries in a database.
|
|
Purpose
|
tVerticaOutput executes the
action defined on the table and/or on the data contained in the
table, based on the flow incoming from the preceding component in
the job.
|
|
Basic settings
|
Property type
|
Either Built-in or
Repository.
Since version 5.6, both the Built-In mode and the Repository mode are
available in any of the Talend solutions.
|
|
|
|
Built-in: No property data stored
centrally.
|
|
|
|
Repository: Select the repository
file in which the properties are stored. The fields that follow are
completed automatically using the data retrieved.
|
|
|
|
Click this icon to open a database connection wizard and store the
database connection parameters you set in the component Basic settings view.
For more information about setting up and storing database
connection parameters, see Talend Studio User Guide.
|
|
|
DB Version
|
Select the version of Vertica you are using from the list.
|
|
|
Use an existing connection
|
Select this check box and in the Component List click the
relevant connection component to reuse the connection details you already defined.
Note
When a Job contains the parent Job and the child Job, if you need to share an existing
connection between the two levels, for example, to share the connection created by the
parent Job with the child Job, you have to:
-
In the parent level, register the database connection to be shared in the
Basic settings view of the connection
component which creates that very database connection.
-
In the child level, use a dedicated connection component to read that
registered database connection.
For an example about how to share a database connection across Job levels, see
Talend Studio User
Guide.
|
|
|
Host
|
Database server IP address
|
|
|
Port
|
Listening port number of DB server.
|
|
|
Database
|
Name of the database
|
|
|
Username and
Password
|
DB user authentication data.
To enter the password, click the […] button next to the
password field, and then in the pop-up dialog box enter the password between double quotes
and click OK to save the settings.
|
|
|
Table
|
Name of the table to be written. Note that only one table can be
written at a time.
|
|
|
Action on table
|
Note
The Action on table list will
not be available if you select the Enable
parallel execution check box in the Advanced settings view.
On the table defined, you can perform one of the following
operations:
Default: No operation is carried
out.
Drop and create table: The table is
removed and created again.
Create table: The table does not
exist and gets created.
Create table if not exists: The
table is created if it does not exist.
Drop table if exists and create:
The table is removed if it already exists and created again.
Clear table: The table content is
deleted.
|
| |
Use “drop cascade”
|
Note
This check box is available when you selected the table drop
related option from the Action on
table list.
Select this check box to remove all objects related to the table
which will be dropped.
|
|
|
Action on data
|
On the data of the table defined, you can perform:
Insert: Add new entries to the
table. If duplicates are found, job stops.
Update: Make changes to existing
entries
Insert or update: Insert a new record. If the record with
the given reference already exists, an update would be made.
Update or insert: Update the record with the given
reference. If the record does not exist, a new record would be inserted.
Delete: Remove entries
corresponding to the input flow.
Copy: Read data from a text file
and insert tuples of entries into the WOS (Write Optimized Store) or
directly into the ROS (Read Optimized Store). This option is ideal
for bulk loading. For further information, see your Vertica SQL
Reference Manual.
Warning
It is necessary to specify at least one
column as a primary key on which the Update and Delete operations are based. You can do that
by clicking Edit Schema and
selecting the check box(es) next to the column(s) you want
to set as primary key(s). For an advanced use, click the
Advanced settings view
where you can simultaneously define primary keys for the
Update and Delete operations. To do that:
Select the Use field
options check box and then in the Key in update column, select the
check boxes next to the column names you want to use as a
base for the Update operation. Do the same in the Key in delete column for the
Delete operation.
|
|
|
Schema and Edit
schema
|
A schema is a row description. It defines the number of fields to be processed and passed on
to the next component. The schema is either Built-In or
stored remotely in the Repository.
Since version 5.6, both the Built-In mode and the Repository mode are
available in any of the Talend solutions.
This component offers the advantage of the dynamic schema feature. This allows you to
retrieve unknown columns from source files or to copy batches of columns from a source
without mapping each column individually. For further information about dynamic schemas,
see Talend Studio
User Guide.
This dynamic schema feature is designed for the purpose of retrieving unknown columns
of a table and is recommended to be used for this purpose only; it is not recommended
for the use of creating tables.
|
|
|
|
Built-In: You create and store the schema locally for this
component only. Related topic: see Talend Studio
User Guide.
|
|
|
|
Repository: You have already created the schema and
stored it in the Repository. You can reuse it in various projects and Job designs. Related
topic: see Talend Studio User Guide.
When the schema to be reused has default values that are integers or functions, ensure that
these default values are not enclosed within quotation marks. If they are, you must remove
the quotation marks manually.
For more details, see https://help.talend.com/display/KB/Verifying+default+values+in+a+retrieved+schema.
|
| |
|
Click Edit schema to make changes to the schema. If the
current schema is of the Repository type, three options are
available:
-
View schema: choose this option to view the
schema only.
-
Change to built-in property: choose this option
to change the schema to Built-in for local
changes.
-
Update repository connection: choose this option to change
the schema stored in the repository and decide whether to propagate the changes to
all the Jobs upon completion. If you just want to propagate the changes to the
current Job, you can select No upon completion and
choose this schema metadata again in the [Repository
Content] window.
|
|
|
Die on error
|
This check box is selected by default. Clear the check box to skip
the row on error and complete the process for error-free rows. If
needed, you can retrieve the rows on error via a Row > Rejects link.
|
|
Advanced settings
|
Additional JDBC Parameters
|
Specify additional JDBC parameters for the database connection
being created.
This option is not available when the Use an
existing connection check box in the Basic settings tab is selected.
|
|
|
Commit every
|
Number of rows to be completed before committing batches of rows
together into the DB. This option ensures transaction quality (but
not rollback) and, above all, better performance at
executions.
|
|
Copy parameters
Note
This area is available only when the Action on data is Copy. For further details about the Copy parameters, see your Vertica SQL
Reference Manual.
|
Abort on error
|
Select this check box to stop the Copy operation on data if a row is rejected and
rolls back this operation. Thus no data is loaded.
|
|
|
Maximum rejects
|
Type in a number to set the REJECTMAX command used by Vertica,
which indicates the upper limit on the number of logical records to
be rejected before a load fails. If not specified or if value is 0,
an unlimited number of rejections are allowed.
|
|
|
No commit
|
Select this check box to prevent the current transaction from
committing automatically.
|
|
|
Exception file
|
Type in the path to, or browse to the file in which messages are
written indicating the input line number and the reason for each
rejected data record.
|
|
|
Exception file node
|
Type in the node of the exception file. If not specified,
operations default to the query’s initiator node.
|
|
|
Rejected data file
|
Type in the path to, or browse to the file in which to write
rejected rows. This file can then be edited to resolve problems and
reloaded.
|
|
|
Rejected data file node
|
Type in the node of the rejected data file. If not specified,
operations default to the query’s initiator node.
|
|
|
Use batch mode
|
Select this check box to activate the batch mode for data
processing. In the Batch Size field
that appears when this check box is selected, you can type in the
number you need to define the batch size to be processed.
Note
This check box is available only when you have selected the
Insert, the Update, the Delete or the Copy option in the Action
on data field.
|
|
|
Additional Columns
|
This option is not offered if you create (with or without drop)
the DB table. This option allows you to call SQL functions to
perform actions on columns, which are not insert, nor update or
delete actions, or action that require particular preprocessing.
|
|
|
|
Name: Type in the name of the
schema column to be altered or inserted as new column
|
|
|
|
SQL expression: Type in the SQL
statement to be executed in order to alter or insert the relevant
column data.
|
|
|
|
Position: Select Before, Replace or After
following the action to be performed on the reference column.
|
|
|
|
Reference column: Type in a
column of reference that the tDBOutput can use to place or replace the new or
altered column.
|
|
|
Use field options
|
Select this check box to customize a request, especially when
there is double action on data.
|
|
|
Enable debug mode
|
Select this check box to display each step during processing
entries in a database.
|
|
|
Support null in “SQL WHERE” statement
|
Select this check box to allow for the Null value in the “SQL
WHERE” statement.
|
|
|
Create projection when create table
|
Select this check box to create a projection for a table to be
created.
Note
This check box is available only when you have selected the
table creation related option from the Action on table list in the Basic settings view and will disppear
when you select the Enable parallel
execution check box in the Advanced settings view.
|
|
|
tStatCatcher 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.
The Dynamic settings table is available only when the
Use an existing connection check box is selected in the
Basic settings view. 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.
|
|
Global Variables
|
NB_LINE: the number of rows processed. This is an After
variable and it returns an integer.
NB_LINE_UPDATED: the number of rows updated. This is an
After variable and it returns an integer.
NB_LINE_INSERTED: the number of rows inserted. This is an
After variable and it returns an integer.
NB_LINE_DELETED: the number of rows deleted. This is an
After variable and it returns an integer.
NB_LINE_REJECTED: the number of rows rejected. This is an
After variable and it returns an integer.
NB_LINE_COPIED: the number of rows copied. This is an
After variable and it returns an integer.
ERROR_MESSAGE: the error message generated by the
component when an error occurs. This is an After variable and it returns a string. This
variable functions only if the Die on error check box is
cleared, if the component has this check box.
A Flow variable functions during the execution of a component while an After variable
functions after the execution of the component.
To fill up a field or expression with a variable, press Ctrl +
Space to access the variable list and choose the variable to use from it.
For further information about variables, see Talend Studio
User Guide.
|
|
Usage
|
This component offers the flexibility benefit of the DB query and
covers all of the SQL queries possible.
This component must be used as an output component. It allows you
to carry out actions on a table or on the data of a table in a
Vertica database. It also allows you to create a reject flow using a
Row > Rejects link to filter
data in error. For an example of tMysqlOutput in use, see Scenario 3: Retrieve data in error with a Reject link.
|
|
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
|
Due to license incompatibility, one or more JARs required to use this component are not
provided. You can install the missing JARs for this particular component by clicking the
Install button on the Component tab view. You can also find out and add all missing JARs easily on
the Modules tab in the Integration perspective
of your studio. For details, see https://help.talend.com/display/KB/How+to+install+external+modules+in+the+Talend+products
or the section describing how to configure the Studio in the Talend Installation and Upgrade
Guide.
|
