-
Notifications
You must be signed in to change notification settings - Fork 2.2k
[Fix][Connector-V2][Elasticsearch]Fix sink configuration for DROP_DATA #7124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Fix][Connector-V2][Elasticsearch]Fix sink configuration for DROP_DATA #7124
Conversation
|
cc @chl-wxp as well. |
|
Thanks @Wudadada for created this PR! Could you follow the guide to open github action on your fork repository? https://github.com/apache/seatunnel/pull/7124/checks?check_run_id=27141444120 |
|
cc @hailin0 as well. |
|
Could you add a test case in Line 475 in ae81879
|
Thanks for pointing out the issues! I encountered a problem in #7140 that is preventing me from debugging, and I am trying to solve the situation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks @Wudadada !
Purpose of this pull request
According to the documentation, the logic for DROP_DATA is to preserve the database structure and delete the data. The original implementation deleted the entire index and recreated it, which caused some field types and parameters to change. This PR corrects the implementation to use the Elasticsearch command to clear index data while preserving the index structure:
POST /your_index_name/_delete_by_query { "query": { "match_all": {} } }Does this PR introduce any user-facing change?
No
How was this patch tested?
By running the connector-elasticsearch-e2e and my local es seatunnel task.
Check list
New License Guide
release-note.