# tExtractXMLField properties for Apache Spark Batch These properties are used to configure tExtractXMLField running in the Spark Batch Job framework. The Spark Batch tExtractXMLField component belongs to the XML 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.

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

View schema: choose this option to view the schema only.
Change to built-in property: choose this option to change the schema to Built-in for local changes.
Update repository connection: 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 No upon completion and choose this schema metadata again in the Repository Content window.

| | --- | --- | | | Built-In: No property data stored centrally. | | | Repository: Select the repository file where the
properties are stored.

When this file is selected, the fields that
follow are pre-filled in using fetched data. | | Schema type 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. | | | 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. | | XML field | Name of the XML field to be processed.

Related topic: see *Talend Studio User
Guide*. | | Loop XPath query | Node of the XML tree, which the loop is based on. | | Mapping | Column: reflects the schema as
defined by the Schema type field.

XPath Query: Enter the fields to be
extracted from the structured input.

Get nodes: Select this check box to
recuperate the XML content of all current nodes specified in the
Xpath query list or select the
check box next to specific XML nodes to recuperate only the content
of the selected nodes. | | Die on error | Select the check box to stop the execution of the Job when an error
occurs. | ## Advanced settings | Ignore the namespaces | Select this check box to ignore namespaces when reading and
extracting the XML data. | | --- | --- | ## 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:

Yarn mode (Yarn client or Yarn cluster):
- When using Google Dataproc, specify a bucket in the Google Storage staging bucket field in the Spark configuration tab.
- When using HDInsight, specify the blob to be used for Job deployment in the Windows Azure Storage configuration area in the Spark configuration tab.
- When using Altus, specify the S3 bucket or the Azure Data Lake Storage for Job deployment in the Spark configuration tab.
- When using Qubole, add a tS3Configuration to your Job to write your actual business data in the S3 system with Qubole. Without tS3Configuration, this business data is written in the Qubole HDFS system and destroyed once you shut down your cluster.
- When using on-premise distributions, use the configuration component corresponding to the file system your cluster is using. Typically, this system is HDFS and so use .
Standalone mode: use the configuration component corresponding to the file system your cluster is using, such as tHDFSConfiguration or tS3Configuration.

If you are using Databricks without any configuration component present in your Job, your business data is written directly in DBFS (Databricks Filesystem).

This connection is effective on a per-Job basis. |