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. The schema is either Built-In or stored remotely in the Repository.

The schema of the data outputted by this component is read-only, id_document and json_document. The json_document column contains the body of the documents read
from ElasticSearch. If you need to explore data from this json_document column, you have to use tExtractJSONFields to extract the data to be
used.

Use an existing
configuration

Select this check box and in the Component
List click the relevant connection component to reuse the connection
details you already defined.

Nodes

Enter the location of the cluster hosting the Elasticsearch system to be used.

Index

Enter the name of the index you want to read documents from.

An index is the largest unit of storage in the Elastisearch system.

Type

Enter the name of the type the documents to be read belong to.

For example, blogpost_en and blogpost_fr can be two types that represent given English blog posts and
French blog posts, respectively.

You can dynamically uses the values of a given column to be document types. If you need to
do so, enter the name of that column into a pair of braces ({}), for example, {blog_author}.

Query

Enter the ElasticSearch query to be performed by this component.

In editing queries, you need to use the syntax required by ElasticSearch along with escape
characters required by Java, and put the query within double quotation marks.

Use SSL/TLS

Select this check box to enable the SSL or TLS encrypted connection.

Then you need to use the tSetKeystore
component in the same Job to specify the encryption information.

For further information about tSetKeystore, see tSetKeystore.

Configuration

Add the parameters accepted by Elasticsearch to perform more customized actions.

For example, enter es.mapping.id in the Key column and true in the
Value column to make the document field/property name
contain the document id. Note that you must put double quotation marks around the entered
information.

For a list of the parameters you can use, see https://www.elastic.co/guide/en/elasticsearch/hadoop/master/configuration.html.

Usage rule

This component is used as a start component and requires an output link..

This component should use a tElasticSearchConfiguration
component present in the same Job to connect to ElasticSearch. You need to select the
Use an existing configuration check box and then select
the tElasticSearchConfiguration component to be
used.

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

This connection is effective on a per-Job basis.