tPostgresPlusOutputBulk

tPostgresPlusOutputBulk properties

The tPostgresplusOutputBulk and tPostgresplusBulkExec 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 tPostgresPlusOutputBulkExec
component, detailed in a separate section. The advantage of using two separate
components is that the data can be transformed before it is loaded in the database.

Component family	Databases/PostgresPlus
Function	Writes a file with columns based on the defined delimiter and the PostgresPlus standards
Purpose	Prepares the file to be used as parameter in the INSERT query to feed the PostgresPlus database.
Basic settings	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 fields that follow are completed automatically using the data retrieved.
	File Name	Name of the file to be generated. Warning 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. Since version 5.6, both the Built-In mode and the Repository mode are available in any of the Talend solutions. 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. 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. 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 details, see https://help.talend.com/display/KB/Verifying+default+values+in+a+retrieved+schema.
Advanced settings	Row separator	String (ex: ” “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.
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. 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. A Flow variable functions during the execution of a component while an After variable functions after the execution of the component.
Usage	This component is to be used along with tPostgresPlusBulkExec component. Used together they offer gains in performance while feeding a PostgresPlus database.
Log4j	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 http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Level.html.

Related scenarios

For use cases in relation with tPostgresplusOutputBulk, see the following scenarios:

Document get from Talend https://help.talend.com

Thank you for watching.

Docs 5.x

0 Comments

Inline Feedbacks

View all comments

tPostgresPlusOutputBulk – Docs for ESB 5.x