July 30, 2023

tELTPostgresqlMap – Docs for ESB 7.x

tELTPostgresqlMap

Builds the SQL SELECT statement using the table schema(s) provided by one or more
tELTPostgresqlInput components.

The three ELT Postgresql components are closely
related, in terms of their operating conditions. These components should be used to
handle Postgresql database table schemas to generate SQL statements, including clauses,
which are to be executed in the database output table defined.

tELTPostgresqlMap Standard properties

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

The Standard
tELTPostgresqlMap component belongs to the ELT family.

The component in this framework is available in all Talend
products
.

Basic settings

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:

  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 Postgresql Map Editor

The ELT Map editor allows you to define the output schema and make a
graphical build of the SQL statement to be executed. The column names of
schema can be different from the column names in the database.

Style link

Select the 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: Links between the schema
and the Web service parameters are in the form of curve.

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

 

Built-in: No property data stored
centrally.

 

Repository: Select the Repository
file where Properties are stored. The following fields are pre-filled in
using fetched data.

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.

Advanced settings

Additional JDBC parameters

Specify additional connection properties for the DB connection you are
creating. This option is not available if you have selected the
Use an existing connection check
box in the Basic settings.

tStatCatcher Statistics

Select this check box to gather the Job processing metadata at a Job
level as well as at each component level.

Global Variables

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.

Usage

Usage rule

tELTPostgresqlMap is used along with
a tELTPostgresqlInput and tELTPostgresqlOutput. Note that the Output
link to be used with these components must correspond strictly to the
syntax of the table name.

Note:

Note that the ELT components do not handle actual data flow but
only schema information.

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 Reading data from databases through context-based dynamic connections and 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