August 16, 2023

tVerticaInput – Docs for ESB 6.x

tVerticaInput

Retrieves data from a Vertica database table based on a SQL query.

tVerticaInput Standard properties

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

The Standard
tVerticaInput component belongs to the Databases family.

The component in this framework is generally available.

Basic settings

Property Type

Select the way the connection details
will be set.

  • Built-In: The connection details will be set
    locally for this component. You need to specify the values for all
    related connection properties manually.

  • Repository: The connection details stored
    centrally in Repository > Metadata will be reused by this component. You need to click
    the […] button next to it and in the pop-up
    Repository Content dialog box, select the
    connection details to be reused, and all related connection
    properties will be automatically filled in.

Save_Icon.png

Click the icon to open a database connection wizard and store the database connection
parameters you set in the component.

For more information about setting up and storing database connection parameters, see
Talend Studio
User Guide.

DB Version

Select the version of the database.

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
.

Host

The IP address or hostname of the database.

Port

The listening port number of the database.

Database

The name of the database.

Schema

The schema of the database.

Username and Password

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.

Schema and Edit schema

A schema is a row description. It defines the number of fields (columns) to
be processed and passed on to the next component. The schema is either Built-In or stored remotely in the Repository.

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

Click Edit schema to make changes to the
schema. Note that if you make changes, the schema automatically becomes built-in.

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

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.

Table Name

The name of the table from which data will be retrieved.

Query Type and Query

Specify the database query statement paying particularly attention to the
properly sequence of the fields which must correspond to the schema definition.

  • Built-In: Fill in the query statement in the
    Query field manually or click the
    […] button next to the Query field
    to build the statement graphically using the SQLBuilder.

  • Repository: Select the relevant query stored in the
    Repository by clicking the […] button next to it and in the
    pop-up Repository Content dialog box, select the query to be
    used, and the Query field will be automatically filled
    in.

If using the dynamic schema feature, the SELECT query must
include the * wildcard, to retrieve all of the
columns from the table selected.

Advanced settings

Additional JDBC Parameters

Specify additional JDBC parameters for the
database connection being created.

This property is not available when the Use an existing connection check box is
selected.

Trim all the String/Char columns

Select this check box to remove leading whitespace and trailing
whitespace from all String/Char columns.

Trim column

Select the check box for corresponding column to remove leading whitespace
and trailing whitespace from it.

This property is not available when the Trim all the String/Char
columns
check box is selected.

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

NB_LINE

The number of rows processed. This is an After variable and it returns an integer.

QUERY

The query statement being processed. This is a Flow variable and it returns a
string.

ERROR_MESSAGE

The error message generated by the component when an error occurs. This is an After
variable and it returns a string.

Usage

Usage rule

This component covers all possible SQL queries for the Vertica
database.

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
.

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


Document get from Talend https://help.talend.com
Thank you for watching.
Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x