# tFileInputJSON MapReduce properties (deprecated) Availability-note[Deprecated](https://help.talend.com/r/en-US/Cloud/labels-on-talend-help-center/availability-deprecated) This content is deprecated. These properties are used to configure tFileInputJSON running in the MapReduce Job framework. The MapReduce tFileInputJSON component belongs to the MapReduce family. The component in this framework is available in all Talend products with Big Data and Talend Data Fabric. Availability-note[Deprecated](https://help.talend.com/r/en-US/Cloud/labels-on-talend-help-center/availability-deprecated) This content is deprecated. The MapReduce framework is deprecated from Talend 7.3 onwards. Use Talend Jobs for Apache Spark to accomplish your integration tasks. ## Basic settings | Property type | Either Built-In or Repository. | | --- | --- | | | Built-In: No property data stored centrally. | | | Repository: Select the repository file where the
properties are stored.

The fields that come after are pre-filled in using the fetched
data.

For further information about the File
Json node, see the section about setting up a JSON file
schema in *Talend Studio*
*User Guide*. | | Schema et 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. When you create a Spark
Job, avoid the reserved word line when naming the
fields.

Click Edit
schema to make changes to the schema. If the current schema is of the Repository type, three options are available:

| | | Built-In: You create and store the schema locally for this component
only. | | | Repository: You have already created the schema and stored it in the
Repository. You can reuse it in various projects and Job designs. | | Read by | Select a way of extracting the JSON data in the file.

| | Folder/File | Enter the path to the file or folder on HDFS from which the data
will be extracted.

If the path you entered points to a folder, all files stored in
that folder will be read.

If the file to be read is a compressed one, enter the file name
with its extension; then tFileInputJSON automatically decompresses it at
runtime. The supported compression formats and their corresponding
extensions are:



Note that you need
to ensure you have properly configured the connection to the Hadoop
distribution to be used in the Hadoop
configuration tab in the Run view. | | Die on error | Select the check box to stop the execution of the Job when an error
occurs.

Clear the check box to skip any rows on error and complete the process for
error-free rows. When errors are skipped, you can collect the rows on error using a Row > Reject link. | | Loop Jsonpath query | Enter the Jsonpath or XPath of the node on which the loop is based.

Note if you have selected Xpath from the Read by drop-down list, the Loop
Xpath query field is displayed instead. | | Mapping | Complete this table to map the columns defined in the schema to the
corresponding JSON nodes.

| ## Advanced settings | Advanced separator (for number) | Select this check box to change the separator used for numbers. By default, the thousands separator is a comma (*,*) and the decimal separator is a period (*.*). | | --- | --- | | Validate date | Select this check box to check the date format strictly against the input schema. | | Encoding | Select the encoding from the list or select Custom and define it manually. | ## Global Variables | Global Variables | 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** | In a
Talend
Map/Reduce Job, it is used as a start component and requires
a transformation component as output link. The other components used along with it must be
Map/Reduce components, too. They generate native Map/Reduce code that can be executed
directly in Hadoop.

Once a Map/Reduce Job is opened in the workspace, tFileInputJSON as well as the MapReduce
family appears in the Palette of
the Studio.

For further information about a
Talend
Map/Reduce Job, see the sections
describing how to create, convert and configure a
Talend
Map/Reduce Job of the
**Talend 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, and non Map/Reduce Jobs. | | --- | --- | | Hadoop Connection | You need to use the Hadoop Configuration tab in the
Run view to define the connection to a given Hadoop
distribution for the whole Job.

This connection is effective on a per-Job basis. | | Prerequisites | The Hadoop distribution must be properly installed, so as to guarantee the interaction
with *Talend Studio*. The following list presents MapR related information for
example.



For further information about how to install a Hadoop distribution, see the manuals
corresponding to the Hadoop distribution you are using. |