-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
enhancement(elasticsearch sink): Add update support to bulk action #21860
enhancement(elasticsearch sink): Add update support to bulk action #21860
Conversation
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.
Hi @blackrez, thank you for the PR. This looks straightforward.
Head branch was pushed to by a user without write access
Head branch was pushed to by a user without write access
Head branch was pushed to by a user without write access
Head branch was pushed to by a user without write access
Head branch was pushed to by a user without write access
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.
Left a few minor suggestions from Docs and approved the PR.
Co-authored-by: DeForest Richards <[email protected]>
Co-authored-by: DeForest Richards <[email protected]>
Co-authored-by: DeForest Richards <[email protected]>
@drichards-87 Thanks for the suggestions. |
Head branch was pushed to by a user without write access
Summary
Like discussed in #17852 I add the update support to the bulk API. We deployed it and it works like we wanted.
Change Type
Is this a breaking change?
How did you test this PR?
We use Elasticsearch with the following config files :
https://gist.github.com/blackrez/8b5ff94e081fe68c7811deb8c9e44079
Does this PR include user facing changes?
Checklist
References