July 30, 2023

tFileOutputARFF – Docs for ESB 7.x


Writes an ARFF file that holds data organized according to the defined

tFileOutputARFF Standard properties

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

The Standard
tFileOutputARFF component belongs to the File family.

The component in this framework is available in all Talend

Basic settings

Property type

Either Built-in or Repository.


Built-in: No property data stored


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


Click this icon to open a connection wizard and store the Excel
file connection parameters you set in the component Basic settings view.

For more information about setting up and storing file connection
parameters, see
Talend Studio User

File name

Name or path to the output file and/or the variable to be used.

For further information about how to define and use a variable in
a Job, see
Talend Studio

User Guide.

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

Attribute Define

Displays the schema you defined in the Edit
dialog box.

Column: Name of the

Type: Data type.

Pattern: Enter the data model
(pattern), if necessary.


Enter the name of the relation.


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

Schema and Edit

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

Click Edit
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


Built-in: You can create the
schema and store it locally for this component. Related topic: see

Talend Studio User


Repository: You have already
created and stored the schema in the Repository. You can reuse it in
various projects and Job flowcharts. Related topic: see

Talend Studio User

Create directory if not exists

This check box is selected by default. It creates a directory to
hold the output table if it does not exist.

Advanced settings

Don’t generate empty file

Select this check box if you do not want to generate empty

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

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

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 +
to access the variable list and choose the variable to use from it.

For further information about variables, see
Talend Studio

User Guide.


Usage rule

Use this component along with a Row link to collect data from another component and
to re-write the data to an ARFF file.

Dynamic settings

Click the [+] button to add a row in the
table and fill the Code field with a context variable
to choose your HDFS connection dynamically from multiple connections planned in your
Job. This feature is useful when you need to access files in different HDFS systems or
different distributions, 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
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
and context variables, see Talend Studio
User Guide.


Outgoing links (from this component to another):

Row: Main.

Trigger: On Subjob Ok; On Subjob
Error; Run if.

Incoming links (from one component to this one):

Row: Main; Reject;

Trigger: On Subjob Ok; On Subjob
Error; Run if; On Component Ok; On Component Error; Synchronize;

For further information regarding connections, see

Talend Studio User


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
perspective of your studio. You can find more details about how to install external modules in
Talend Help Center (https://help.talend.com)

Related scenario

For tFileOutputARFF related scenario, see Displaying the content of a ARFF file.

Document get from Talend https://help.talend.com
Thank you for watching.
Notify of
Inline Feedbacks
View all comments
Would love your thoughts, please comment.x