tNamedPipeOutput Standard properties

Use existing pipe connection

Select this check box to use an existing named-pipe in the Pipe component list, or clear this check box to specify a named-pipe in Pipe name field.

Pipe component

Select an existing named-pipe component from the list.

Pipe name

Fill in the field with the name of an existing named-pipe.

Row separator

String (ex: "\n"on Unix) to distinguish rows in the output file.

Field separator

Character, string or regular expression to separate fields of the output file.

CSV options

Select this check box to take into account all parameters specific to CSV files, in particular Escape char and Text enclosure parameters.

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.

Click Sync columns to retrieve the schema from the previous component connected in the Job.

Built-in: The schema will be 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 in various projects and Job flowcharts. For more information about a component schema in its Basic settings tab, see Basic settings tab.

Delete pipe if it exists

Select this check box to avoid duplicate named-pipe.

Boolean type

Select a boolean type from the list.

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

NB_LINE: the number of rows read by an input component or transferred to an output component. This is a Flow variable and it returns an integer.

PIPE_NAME: the name of the named-pipe. This is a Flow variable and it returns a string.

PIPE_NATIVE_NAME: the native name of the named-pipe. This is a Flow variable and it returns a string.

PIPE_OUTPUTSTREAM: the output stream of the named-pipe. This is a Flow variable and it returns an object.

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 rule

This component is usually connected to another component in a subJob that reads data from a source.

Dynamic settings

Click the [+] button to add a row in the table and fill the Code field with a context variable to choose your pipe connection dynamically from multiple connections planned in your Job.

The Dynamic settings table is available only when the Use existing pipe connection check box is selected in the Basic settings view. When a dynamic parameter is defined, the Pipe 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.

Due to license incompatibility, one or more JARs required to use this component are not provided. You can install the missing JARs for this particular component by clicking the Install button on the Component tab view. You can also find out and add all missing JARs easily on the Modules tab in the Integration perspective of Talend Studio. For details, see Installing external modules.