alibaba / alibaba/DataX

Mysql8.0同步数据到Elasticsearch8.3.3错误

Open
#1,481 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
17.4k
Forks
5.7k
PR merge metrics
No merged PRs in 30d

Description

如题,Elasticsearch8的版本中已经去除了type:'_doc'字段,在使用Datax同步时一直报错

- 使用示例job文件测试时报错如下:
![0764dcffd683dd92e24a69a40ea4a9d](https://user-images.githubusercontent.com/9602672/185333892-9ced220e-3c75-4e0e-abf3-c0f2ac00d312.png)

- 在job.json文件中删除掉type:'_doc'字段依然报错:

![d962941448bcf309383ee1e651763f0](https://user-images.githubusercontent.com/9602672/185334069-ad74bedb-3a9d-41fb-b7e9-cd99b9bd741d.png)

测试使用Elasticsearch7版本的同步数据正常;请尽快修改以支持Elasticsearch8版本的数据同步。

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the example job.json and the Elasticsearch writer path used by DataX, then compare the reported Elasticsearch 8 errors with the working Elasticsearch 7 synchronization. Done means a MySQL-to-Elasticsearch 8.3.3 job runs successfully without the removed type field.

Written by the indexing model from the issue text.

Assessment

Tech stack
elasticsearch, java, mysql
Domain
data-engineering, databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.