tMatchIndex properties for Apache Spark Batch

Define a storage configuration component

Select the configuration component to be used to provide the configuration information for the connection to the target file system such as HDFS.

If you leave this check box clear, the target file system is the local system.

The configuration component to be used must be present in the same Job. For example, if you have dropped a tHDFSConfiguration component in the Job, you can select it to write the result in a given HDFS system.

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 Sync columns to retrieve the schema from the previous component connected in the Job.

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.

Read-only columns are added to the output schema:

• INTERNAL_ID: This column holds the identifier generated for each record in the input data.

• BKV: This column holds the blocking key value generated for each record in the input data.

• BEST_SUFFIX: This column holds the smallest suffix generated from the blocking key value. The suffixes are used to group records.

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.

ElasticSearch configuration

Nodes: Enter the location of the cluster hosting the ElasticSearch system to be used.

Index: Enter the name of the index to be created in ElasticSearch.

Select the Reset index check box to clean the ElasticSearch index specified in the Index field.

Note that the Talend components support the Elasticsearch 6.4.x version for Spark Streaming Jobs, and Elasticsearch 7.x and 8.x versions for Spark Batch Jobs.

Pairing

Pairing model folder: Set the path to the folder which has the model files generated by the tMatchPairing component.

If you want to store the model in a specific file system, for example S3 or HDFS, you must use the corresponding component in the Job and select the Define a storage configuration component check box in the component basic settings.

The button for browsing does not work with the Spark Local mode; if you are using the other Spark Yarn modes that Talend Studio supports with your distribution, ensure that you have properly configured the connection in a configuration component in the same Job. Use the configuration component depending on the filesystem to be used.

Maximum ElasticSearch bulk size

Maximum number of records for bulk indexing.

tMatchIndex uses bulk mode to index data so that big batches of data can be quickly indexed in ElasticSearch.

It is recommended to leave the default value. If the Job execution ends with an error, reduce the value for this parameter.

Usage rule

This component is used as an end component and requires an input link.

This component, along with the Spark Batch component Palette it belongs to, appears only when you are creating a Spark Batch Job.

Spark Batch Connection

This connection is effective on a per-Job basis.