# tFileInputJSON Standard properties

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

The Standard tFileInputJSON component belongs to the Internet and the File families.

The component in this framework is available in all Talend products.

## Basic settings

| Properties | Description |
| --- | --- |
| Property Type | <ul> <li> <p>Either <span>Built-In</span> or <span>Repository</span>. </p> </li> <li> <p> <span>Built-In</span>: No property data stored centrally.</p> </li> <li> <p> <span>Repository</span>: Select the repository file where the            properties are stored.</p> </li> </ul> |
| Schema and Edit 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><ul> <li> <p> <span>Built-In</span>: You create and store the schema locally for this component                only.</p> </li> <li> <p> <span>Repository</span>: You have already created the schema and stored it in the                Repository. You can reuse it in various projects and Job designs.</p> </li> </ul><br><br>Click Edit schema to make changes to<br>the schema. If you make changes, the schema automatically becomes built-in.<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.</p> <p>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> |
| Read By | Select a way of extracting JSON data in the<br>file.<br><br><ul> <li> <p> <span>JsonPath</span>: Extracts JSON data based on the                                JSONPath query. With this option selected, you need to select a                                JSONPath API version from the <span>API version</span>                                drop-down list. It is recommended to read data by JSONPath in order                                to gain better performance.</p> </li> <li> <p> <span>Xpath</span>: Extracts JSON data based on the XPath                                query.</p> </li> <li> <p> <span>JsonPath without loop</span>: Extracts JSON data                                based on the JSONPath query without setting a loop node.</p> </li> </ul> |
| Use Url | Select this check box to retrieve data directly from the Web. |
| URL | Enter the URL path from which you will retrieve data.<br><br>This field is available only when the Use Url check box is selected. |
| Filename | Specify the file from which you will retrieve data.<br><br>This field is not visible if the Use<br>Url check box is selected.<br><br>Information noteWarning:<br><br><ul> <li>Use absolute path (instead of relative path) to avoid possible                           errors.</li> <li>When using <span>Xpath</span>, make sure the fields in your                           JSON file do not start with numbers, to avoid the following error when                           running the Job: <span>The content of elements must consist of                              well-formed character data or markup.</span></li> </ul> |
| Loop Json query | Enter the JSONPath or XPath of the node on which the loop is based.<br><br>Note if you have selected Xpath from the Read by drop-down list, the Loop<br>Xpath query field is displayed instead. |
| Mapping | Complete this table to map the columns defined in the schema to the<br>corresponding JSON nodes.<br><br><ul> <li> <p> <span>Column</span>: The <span>Column</span> cells are automatically filled with the defined schema                    column names.</p> </li> <li> <p> <span>Json query</span>/<span>JSONPath query</span>: Specify the JSONPath node that holds the                    desired data. For more information about JSONPath expressions, see <a href="http://goessner.net/articles/JsonPath/" target="_blank">http://goessner.net/articles/JsonPath/</a>.</p> <p>This column is available only when <span>JsonPath</span> is selected from the <span>Read                        By</span> list.</p> </li> <li> <p> <span>XPath query</span>: Specify the XPath node that                    holds the desired data.</p> <p>This column is available only when <span>Xpath</span> is selected from the <span>Read                        By</span> list.</p> </li> <li> <p> <span>Get Nodes</span>: Select this check box to                    extract the JSON data of all the nodes or select the check box next to a                    specific node to extract the data of that node.</p> <p>This column is available only when <span>Xpath</span> is selected from the <span>Read                        By</span> list.</p> </li> </ul> |
| Die on error | Select this check box to stop the execution of the Job when an<br>error occurs. Clear the check box to skip the row on error and complete the<br>process for error-free rows. If needed, you can collect the rows on error using<br>a Row &gt; Reject link. |

## Advanced settings

| Properties | Description |
| --- | --- |
| JDK version | Select the JDK version to be used. Note that a Standalone Nashorn JAR will be<br>imported if you select JDK 11 and above. For<br>JDK 8 to 11, Nashorn dependency is built in the<br>JDK.<br><br>This option is available when you select JsonPath without<br>loop from the Read By drop-down list in<br>the Basic settings view.<br><br>Information noteNote:<br><br><ul> <li>This option is available only when you have installed the 8.0.1-R2023-01                        <span>Talend Studio</span> Monthly update or a later one delivered by <span>Talend</span>. For more information, check with your administrator.</li> <li>The JDK version changes from <span>JDK 15 and above</span> to                              <span>JDK 11 and above</span> and from <span>JDK 8 -                              JDK 14</span> to <span>JDK 8 to 11</span> only when you                           have installed the 8.0.1-R2023-02 <span>Talend Studio</span> Monthly update or a later one delivered by <span>Talend</span>. For more information, check with your administrator. </li> </ul> |
| Advanced separator (for numbers) | 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 (*.*).<br><br><br>Thousands separator: define<br>separators for thousands.<br><br><br>Decimal separator: define separators<br>for decimals. |
| Use the loop node as root | Select this check box to use the loop node as the root for querying the file.<br><br>The loop node is set in the Loop Json query text frame<br>in the Basic Settings view. If this option is checked,<br>only the child elements of the loop node are available for querying; otherwise,<br>both the parent elements and the child elements of the loop node can be<br>queried. You can specify a parent element through JSON path syntax.<br><br>This check box is available only when JsonPath is<br>selected in the Read By drop-down list of the<br>Basic settings view. |
| Validate date | Select this check box to check the date format strictly against the input schema.<br><br>This check box is available only if the Read By<br>XPath check box is selected. |
| Encoding | Select the encoding type from the list or select Custom and define it manually. This field is compulsory for<br>DB data handling. |
| Include the Nashorn library | Select this option to include the Nashorn library. This option is necessary if you are using JDK<br>15 or a higher version.<br><br>This option is available when JsonPath without loop is<br>selected from the Read By drop-down list in the<br>Basic settings view. |
| tStatCatcher Statistics | Select this check box to gather the Job processing metadata at a Job<br>level as well as at each component level. |

## Global Variables

| Variables | Description |
| --- | --- |
| Global Variables | NB\_LINE:<br>the number of rows processed. This is an After variable and it returns an integer.<br><br><br>ERROR\_MESSAGE: the error message generated by the<br>component when an error occurs. This is an After variable and it returns a string. This<br>variable functions only if the Die on error checkbox is<br>cleared, if the component has this checkbox.<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 variable, press Ctrl+Space to access the variable list and choose the variable to use from<br>it.<br><br>For more information about variables, see [Using contexts and variables](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/contexts-and-variables). |

## Usage

| Usage guidance | Description |
| --- | --- |
| **Usage rule** | This component is a start component of a Job and always needs an<br>output link. |