tFileOutputRaw Standard properties - 7.1

Raw

author
Talend Documentation Team
EnrichVersion
7.1
EnrichProdName
Talend Big Data
Talend Big Data Platform
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Open Studio for Big Data
Talend Open Studio for Data Integration
Talend Open Studio for ESB
Talend Open Studio for MDM
Talend Real-Time Big Data Platform
task
Data Governance > Third-party systems > File components (Integration) > Raw components
Data Quality and Preparation > Third-party systems > File components (Integration) > Raw components
Design and Development > Third-party systems > File components (Integration) > Raw components
EnrichPlatform
Talend Studio

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

The Standard tFileOutputRaw component belongs to the File family.

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

Basic settings

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: No property data stored centrally.

 

Repository: Select the repository file where the properties are stored. The fields that follow are completed automatically using the data retrieved.

Filename

The name of and path to the output file to be processed, which you can enter manually between double quotes or browse and select by clicking the [...] button.

Warning: Use absolute path (instead of relative path) for this field to avoid possible errors.

Encoding

If the output is a string, select the encoding type from the list or select Custom and define it manually.

Die on error

Select this check box to stop the execution of the Job when an error occurs. Clear the check box to skip the row on error and complete the process for error-free rows. If needed, you can collect the rows on error using a Row > Reject link.

To catch the FileNotFoundException, you also need to select this check box.

Advanced settings

tStatCatcher Statistics

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

Global Variables

Global Variables

FILENAME_PATH: the path of the input file. This is an After variable and it returns a string.

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

Use the tFileOutputRaw component to receive data coming from a data source that provides its data in a single column.

Limitation

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 your studio. For details, see Installing external modules. .