tLogRow Storm properties

Logs and errors (Integration)

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

These properties are used to configure tLogRow running in the Storm Job framework.

The Storm tLogRow component belongs to the Logs & Errors family.

The component in this framework is available in Talend Real Time Big Data Platform and Talend Data Fabric.

Basic settings

Schema and Edit schema

A schema is a row description. It defines the number of fields (columns) 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.

This component offers the advantage of the dynamic schema feature. This allows you to retrieve unknown columns from source files or to copy batches of columns from a source without mapping each column individually. For further information about dynamic schemas, see Talend Studio User Guide.

This dynamic schema feature is designed for the purpose of retrieving unknown columns of a table and is recommended to be used for this purpose only; it is not recommended for the use of creating tables.

 

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.

Sync columns Click to synchronize the output file schema with the input file schema. The Sync function is available only when the component is linked with the preceding component using a Row connection.
Basic Displays the output flow in basic mode.
Table Displays the output flow in table cells.
Vertical

Displays each row of the output flow as a key-value list.

With this mode selected, you can choose to show either the unique name or the label of component, or both of them, for each output row.

Separator

(For Basic mode only)

Enter the separator which will delimit data on the Log display.

Print header

(For Basic mode only)

Select this check box to include the header of the input flow in the output display.

Print component unique name in front of each output row

(For Basic mode only)

Select this check box to show the unique name the component in front of each output row to differentiate outputs in case several tLogRow components are used.

Print schema column name in front of each value

(For Basic mode only)

Select this check box to retrieve column labels from output schema.

Use fixed length for values

(For Basic mode only)

Select this check box to set a fixed width for the value display.

Usage

Usage rule

This component can be used as intermediate step in a data flow or as a n end object in the Job flowchart.

If you have subscribed to one of the Talend solutions with Big Data, you can also use this component as a Storm component. In a Talend Storm Job, this component is used as an intermediate or an end step. It generates native Storm code that can be executed directly in a Storm system.

The Storm version does not support the use of the global variables.

You need to use the Storm Configuration tab in the Run view to define the connection to a given Storm system for the whole Job.

This connection is effective on a per-Job basis.

For further information about a Talend Storm Job, see the sections describing how to create and configure a Talend Storm Job of the Talend Open Studio for Big Data Getting Started Guide .

Note that in this documentation, unless otherwise explicitly stated, a scenario presents only Standard Jobs, that is to say traditional Talend data integration Jobs.