tPostgresPlusInput Standard properties
These properties are used to configure tPostgresPlusInput running in the Standard Job framework.
The Standard tPostgresPlusInput component belongs to the Databases family.
The component in this framework is available in all Talend products.
Basic settings
Database |
Select the desired database type from the list and click Apply. |
Property type |
Either Built-in or Repository . |
|
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 Centralizing database metadata. |
Use an existing connection |
Select this check box and in the Component List drop-down list, select the desired connection component to reuse the connection details you already defined. Information noteNote: When a Job contains the parent Job and the child Job, do the following if you
want to share an existing connection between the parent Job and the child Job (for example,
to share the connection created by the parent Job with the child Job).
For an example about how to share a database connection across Job levels, see Sharing a database connection. |
DB Version |
List of database versions. |
Host |
Database server IP address. |
Port |
Listening port number of DB server. |
Database |
Name of the database. |
Schema |
Exact name of the schema. |
Username and Password |
DB user authentication data. To enter the password, click the [...] button next to the password field, enter the password in double quotes in the pop-up dialog box, 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. When you create a Spark Job, avoid the reserved word line when naming the fields. Click Edit schema to make changes to the schema. If the current schema is of the Repository type, three options are available:
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 Dynamic schema. 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: The schema is created and stored locally for this component only. For more information about a component schema in its Basic settings tab, see Basic settings tab. |
|
Repository: The schema already exists and is stored in the Repository, hence can be reused. For more information about a component schema in its Basic settings tab, see Basic settings tab. |
Table name |
Name of the table to be read. |
Query type and Query |
Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. 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 created. This property is not available when the Use an existing connection check box in the Basic settings view is selected. |
Use cursor |
When selected, helps to decide the row set to work with at a time and thus optimize performance. |
Trim all the String/Char columns |
Select this check box to remove leading and trailing whitespace from all the String/Char columns. |
Trim column |
Remove leading and trailing whitespace from defined columns. |
tStat Catcher Statistics |
Select this check box to collect log data at the component level. |
Global Variables
Global Variables |
NB_LINE: the number of rows read by an input component or transferred to an output component. 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. 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 more information about variables, see Using contexts and variables. A Flow variable functions during the execution of a component while an After variable functions after the execution of the component. |
Usage
Usage rule |
This component covers all possible SQL queries for Postgresql databases. |
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 Dynamic schema and Creating a context group and define context variables in it. |