tLogRow Storm properties (deprecated)
These properties are used to configure tLogRow running in the Storm Job framework.
The Storm
tLogRow component belongs to the Logs & Errors family.
This component is available in Talend Real Time Big Data Platform and Talend Data Fabric.
The Storm framework is deprecated from Talend 7.1 onwards. Use Talend Jobs for Apache Spark Streaming to accomplish your Streaming related tasks.
Basic settings
Schema and Edit schema |
A schema is a row description. It defines the number of fields Click Edit
This This |
Built-In: You create and store the schema locally for this component |
|
Repository: You have already created the schema and stored it in the |
|
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 |
Separator (For Basic mode only) |
Enter the separator which will delimit data on the Log |
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 (For Basic mode only) |
Select this check box to show the unique name the component in |
Print schema column name in front of each (For Basic mode only) |
Select this check box to retrieve column labels from output |
Use fixed length for values (For Basic mode only) |
Select this check box to set a fixed width for the value |
Usage
Usage rule |
This component can be used as intermediate step in a data flow or If you have subscribed to one of the The Storm version does not support the use of the global variables. You need to use the Storm Configuration tab in the This connection is effective on a per-Job basis. For further information about a Note that in this documentation, unless otherwise explicitly stated, a scenario presents |