Help Center/ Cloud Data Migration/ User Guide/ Creating a Job in a CDM Cluster/ Configuring CDM Destination Job Parameters/ To Elasticsearch/CSS
Updated on 2024-10-24 GMT+08:00
View PDF
Share

To Elasticsearch/CSS

If the destination link of a job is a link described in Elasticsearch Link Parameters or CSS Link Parameters, configure the destination job parameters based on Table 1.

The parameters required for table/file migration are different from those for entire DB migration. The following table lists the parameters for table/file migration. The actual parameters are subject to those displayed on the console.

Table 1 Job parameters when Elasticsearch/CSS is the destination

Parameter

Description

Example Value

Index

Elasticsearch index, which is similar to the name of a relational database. CDM supports automatic creation of indexes and field types. The index and field type names can contain only lowercase letters.

index

Type

Elasticsearch type, which is similar to the table name of a relational database. The type name can contain only lowercase letters.

NOTE:

Elasticsearch 7.x and later versions do not support custom types. Instead, only the _doc type can be used. In this case, this parameter does not take effect even if it is set.

type

Pipeline ID

ID of the pipeline used to convert the format of the data transferred to Elasticsearch.

If the destination is Elasticsearch, you need to create a pipeline ID in Kibana first.

If the destination is CSS, you do not need to create a pipeline ID. Instead, enter the name of the configuration file, which is name by default.

If the destination is Elasticsearch: pipeline_id

If the destination is CSS: name (name of the configuration file)

Write ES with Routing

If you enable this function, a column can be written to Elasticsearch as a route.

NOTE:

Before enabling this function, create indexes at the destination to improve the query efficiency.

No

Route Column

This parameter is available when Write ES with Routing is set to Yes. It specifies the destination routing column. If the destination index exists but the column information cannot be obtained, you can manually enter the column. The route column can be empty. If it is empty, no routing value is specified for the data written to Elasticsearch.

value1

Periodically Create Index
For streaming jobs that continuously write data to Elasticsearch, CDM periodically creates indexes and writes data to the indexes, which helps you delete expired data. The indexes can be created based on the following periods:
  • Every hour: CDM creates indexes on the hour. The new indexes are named in the format of Index name+Year+Month+Day+Hour, for example, index2018121709.
  • Every day: CDM creates indexes at 00:00 every day. The new indexes are named in the format of Index name+Year+Month+Day, for example, index20181217.
  • Every week: CDM creates indexes at 00:00 every Monday. The new indexes are named in the format of Index name+Year+Week, for example, index201842.
  • Every month: CDM creates indexes at 00:00 on the first day of each month. The new indexes are named in the format of Index name+Year+Month, for example, index201812.
  • Do not create: Do not create indexes periodically.

When extracting data from a file, you must configure a single extractor, which means setting Concurrent Extractors to 1. Otherwise, this parameter is invalid.

Every hour