tELTVerticaMap Properties - 6.3

Talend Open Studio for Big Data Components Reference Guide

Talend Open Studio for Big Data
Data Governance
Data Quality and Preparation
Design and Development
Talend Studio

Component Family


Basic settings

DB Version

Select the version of the Vertica database being used.


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.


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:

  1. 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.

  2. 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.


ELT Vertica Map Editor

The ELT Map editor allows you to define the output schema as well as build graphically the SQL statement to be executed. The column names of the schema can be different from the column names in the database.


Style link

Select a way in which links are displayed.

  • Auto: By default, the links between the input and output schemas and the Web service parameters are in the form of curves.

  • Bezier curve: The links between the schema and the Web service parameters are in the form of curve.

  • Line (fastest): The links between the schema and the Web service parameters are in the form of straight lines.

    This option slightly optimizes performance.


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 database connection fields that follow are completed automatically using the data retrieved.



Type in the IP address or hostname of the database.



Type in the listening port number of the database.



Type in the name of the database you want to use.


Additional JDBC Parameters

Specify additional connection properties for the database connection you are creating.


Username and Password

Type in the database 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.

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. 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.


tELTVerticaMap is used along with tELTVerticaInput and tELTVerticaOutput. Note that the Output link to be used with these components must correspond strictly to the syntax of the table name.


The ELT components do not handle actual data flow but only schema information.


If you are using a subscription-based version of the Studio, 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

Connecting ELT components

The ELT components do not handle any data as such but table schema information that will be used to build the SQL query to execute. Therefore the only connection required to connect these components together is a simple link.

Note that the output name you give to the link when creating it should always be the exact name of the table to be accessed as this parameter will be used in the SQL statement generated.

For the related topic, see Talend Studio User Guide.

Mapping and joining tables

In the ELT Mapper, you can select specific columns from the input schema and include them in the output schema.

  • As you would do it in the regular Map editor, simply drag & drop the columns from the input schema towards the output table defined.

  • Use the Ctrl or Shift key for multiple selection of contiguous or non-contiguous table columns.

You can implement explicit joins to retrieve various data from different tables.

  • Select the Explicit join check box for the relevant column of the input schema and then select a type of join from the join list in the upper right corner of the input schema.

  • Possible joins include: INNER JOIN, LEFT OUTER JOIN, RIGHT OUTER JOIN, FULL OUTER JOIN and CROSS JOIN. By default, the INNER JOIN is selected.

You can also create alias tables to retrieve various data from the same table.

  • In the input area, click the [+] button in the upper left corner of the map editor to create a new alias.

  • Select the table on which the alias is based.

  • Type in a new name for the alias table, preferably not the same as the main table.

Adding where and other clauses

You can also restrict the Select statement based on a Where clause and/or other clauses such as Group By, Order By, etc. by clicking the Add filter row button at the top of the output table in the map editor.

To add a restriction based on a Where clause, click the Add filter row button and select Add a WHERE clause from the pop-up menu.

To add a restriction based on Group By, Order By etc., click the Add filter row button and select Add an other(GROUP...) clause from the pop-up menu.

Make sure that all input components are linked correctly to the ELT Map component to be able to implement all inclusions, joins and clauses.

Generating the SQL statement

The mapping of elements from the input schemas to the output schemas creates instantly the corresponding SELECT statement. The clauses are also included automatically.