Skip to main content Skip to complementary content

tPostgresqlOutputBulk

Prepares the file to be used as parameters in the INSERT query to feed the Postgresql database.

The tPostgresqlOutputBulk writes a file with columns based on the defined delimiter and the Postgresql standards.

The tPostgresqlOutputBulk and tPostgresqlBulkExec components are generally used together as part of a two step process. In the first step, an output file is generated. In the second step, this file is used in the INSERT operation used to feed a database. These two steps are fused together in the tPostgresqlOutputBulkExec component, detailed in a separate section. The advantage of having two separate steps is that it makes it possible to transform data before it is loaded in the database.

tPostgresqlOutputBulk Standard properties

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

The Standard tPostgresqlOutputBulk component belongs to the Databases family.

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

Information noteNote: This component is a specific version of a dynamic database connector. The properties related to database settings vary depending on your database type selection. For more information about dynamic database connectors, see DB Generic components.

Basic settings

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

File Name

Name of the file to be generated.

Information noteWarning:

This file is generated on the local machine or a shared folder on the LAN.

Append

Select this check box to add the new rows at the end of the file.

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

    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.

  • Built-In: You create and store the schema locally for this component only.

  • Repository: You have already created the schema and stored it in the Repository. You can reuse it in various projects and Job designs.

    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 information, see Retrieving table schemas.

Advanced settings

Properties Description

Row separator

String (ex: "\n"on Unix) to distinguish rows.

Field separator

Character, string or regular expression to separate fields.

Include header

Select this check box to include the column header to the file.

Encoding

Select the encoding from the list or select Custom and define it manually. This field is compulsory for DB data handling.

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 about context variables, see Using contexts and variables.

Note that when parallel execution is enabled, it is not possible to use global variables to retrieve return values in a subJob.

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

Global Variables

Variables Description

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.

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 more information about variables, see Using contexts and variables.

Usage

Usage guidance Description

Usage rule

This component is to be used along with tPostgresqlBulkExec component. Used together they offer gains in performance while feeding a Postgresql database.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here