tExtractJSONFields properties for Apache Spark Batch
These properties are used to configure tExtractJSONFields running in the Spark Batch Job framework.
The Spark Batch tExtractJSONFields component belongs to the Processing family.
The component in this framework is available in all subscription-based Talend products with Big Data and Talend Data Fabric.
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. |
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. 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.
|
JSON field |
List of the JSON fields to be extracted. |
Loop Jasonpath 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.
|
Die on error |
Select the check box to stop the execution of the Job when an error occurs. |
Advanced settings
Encoding |
Select the encoding from the list or select Custom and define it manually. This field is compulsory for database data handling. The supported encodings depend on the JVM that you are using. For more information, see https://docs.oracle.com. |
Usage
Usage rule |
This component is used as an intermediate step. This component, along with the Spark Batch component Palette it belongs to, appears only when you are creating a Spark Batch Job. Note that in this documentation, unless otherwise explicitly stated, a scenario presents only Standard Jobs, that is to say traditional Talend data integration Jobs. |
Spark Connection |
In the Spark
Configuration tab in the Run
view, define the connection to a given Spark cluster for the whole Job. In
addition, since the Job expects its dependent jar files for execution, you must
specify the directory in the file system to which these jar files are
transferred so that Spark can access these files:
This connection is effective on a per-Job basis. |