Document metadata

Complete this table to select the input columns to be used to provide metadata for each
document. This table is typically used along with the json_document option from the Output
document drop-down list in the Basic
settings view.

The Column column is automatically fed with the columns
of the input schema. Then in the As metadata column, you
need to select the check box(es) that correspond to the column(s) to be used.

In the Metadata type column, select which type of
document metadata each column is used to provide.

For further information about the metadata types of an Elasticsearch document, see https://www.elastic.co/guide/en/elasticsearch/guide/current/_document_metadata.html.

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 an end component and requires an input 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.

Basice settings

Schema and Edit
Schema

Use an existing
configuration

Nodes

Index

Type

Output document

Spark Connection

This connection is effective on a per-Job basis.

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.

Built-In: You create and store the
schema locally for this component only. Related topic: see
Talend Studio

User Guide.

Repository: You have already created
the schema and stored it in the Repository. You can reuse it in various projects and
Job designs. Related topic: see
Talend Studio

User Guide.

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.

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 in which you want to write documents.

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

Type

Enter the name of the type the documents to be written 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}.

Output document

Select how the document is written into Elasticsearch.

Document metadata

Complete this table to select the input columns to be used to provide metadata for each
document. This table is typically used along with the json_document option from the Output
document drop-down list in the Basic
settings view.

The Column column is automatically fed with the columns
of the input schema. Then in the As metadata column, you
need to select the check box(es) that correspond to the column(s) to be used.

In the Metadata type column, select which type of
document metadata each column is used to provide.

For further information about the metadata types of an Elasticsearch document, see https://www.elastic.co/guide/en/elasticsearch/guide/current/_document_metadata.html.

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 an end component and requires an input 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 Streaming component Palette it belongs to, appears
only when you are creating a Spark Streaming 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.