# tLogRow MapReduce properties

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

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

The component in this framework is available in all subscription-based Talend products with Big Data and Talend Data Fabric.

## Basic settings

| Schema and Edit<br>schema | A schema is a row description. It defines the number of fields<br>(columns) to be processed and passed on to the next component. When you create a Spark<br>Job, avoid the reserved word line when naming the<br>fields.<br><br>Click Edit<br>schema to make changes to the schema. If the current schema is of the Repository type, three options are available:<br><br><ul> <li> <p> <span>View schema</span>: choose this                option to view the schema only.</p> </li> <li> <p> <span>Change to built-in property</span>:                choose this option to change the schema to <span>Built-in</span> for local changes.</p> </li> <li> <p> <span>Update repository connection</span>:                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 <span>No</span> upon completion and choose this schema metadata                again in the <span>Repository Content</span>                window.</p> </li> </ul><br><br>This<br>component offers the advantage of the dynamic schema feature. This allows you to<br>retrieve unknown columns from source files or to copy batches of columns from a source<br>without mapping each column individually. For further information about dynamic schemas,<br>see *Talend Studio*<br>*User Guide*.<br><br>This<br>dynamic schema feature is designed for the purpose of retrieving unknown columns of a<br>table and is recommended to be used for this purpose only; it is not recommended for the<br>use of creating tables. |
| --- | --- |
|  | Built-In: You create and store the schema locally for this component<br>only. |
|  | Repository: You have already created the schema and stored it in the<br>Repository. You can reuse it in various projects and Job designs. |
| Sync columns | Click to synchronize the output file schema with the input file schema. The<br>Sync function is available only when the component is linked with the preceding<br>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.<br><br>With this mode selected, you can choose to show either the<br>unique name or the label of component, or both of them, for each output<br>row. |
| Separator<br><br>(For Basic mode only) | Enter the separator which will delimit data on the Log<br>display. |
| Print header<br><br>(For Basic mode only) | Select this check box to include the header of the input flow in the output<br>display. |
| Print component unique name in front of each output<br>row<br><br>(For Basic mode only) | Select this check box to show the unique name the component in<br>front of each output row to differentiate outputs in case several tLogRow components are used. |
| Print schema column name in front of each<br>value<br><br>(For Basic mode only) | Select this check box to retrieve column labels from output<br>schema. |
| Use fixed length for values<br><br>(For Basic mode only) | Select this check box to set a fixed width for the value<br>display. |

## Advanced settings

| Use local timezone for date | Select this check box to use the local date of the machine in which your Job is executed. If leaving this check box clear, UTC is automatically used to format the Date-type data. |
| --- | --- |

## Global Variables

| Global Variables | ERROR\_MESSAGE: the error message generated by the component when an<br>error occurs. This is an After variable and it returns a string. This variable functions<br>only if the Die on error check box<br>is cleared, if the component has this check<br>box.<br><br>A Flow variable functions during the execution of a component<br>while an After variable functions after the execution of the component.<br><br>To fill up a field or expression with a<br>variable, press Ctrl + Space to<br>access the variable list and choose the variable to use from it.<br><br>For further information about variables, see *Talend Studio*<br>*User Guide*. |
| --- | --- |

## Usage

| **Usage rule** | This component can be used as intermediate step in a data flow<br>or as a n end object in the Job flowchart.<br><br>In a<br>Talend<br>Map/Reduce Job, this component is used as an intermediate or<br>an end step. It generates native Map/Reduce code that can be executed directly in<br>Hadoop.<br><br>You need to use the Hadoop Configuration tab in the<br>Run view to define the connection to a given Hadoop<br>distribution for the whole Job.<br><br>This connection is effective on a per-Job basis.<br><br>For further information about a<br>Talend<br>Map/Reduce Job, see the sections<br>describing how to create, convert and configure a<br>Talend<br>Map/Reduce Job of the<br>**Talend Open Studio for Big Data Getting Started Guide**.<br><br>Note that in this documentation, unless otherwise<br>explicitly stated, a scenario presents only Standard Jobs,<br>that is to say traditional<br>Talend<br>data integration Jobs, and non Map/Reduce Jobs. |
| --- | --- |