-
Notifications
You must be signed in to change notification settings - Fork 437
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
ES Document version is set to Kafka record offset #499
Comments
I implemented the solution in my code and it works like a charm. It saved my life. Thanks a lot for this @michaelfortin. |
I also face the same issue. When can we expect a fix for this |
Hi, I have written an PR for this feature and tested the package locally. This is the PR: #628 |
What can be done to get this PR merged? |
I will probably have to create a Jira ticket for this to be noticed... |
+++ |
connector version: 11.0.0
When using
"key.ignore": false
and"write.method": "insert"
, the connector set the document version (version appearing in Elasticsearch) to the record offset in Kafka, for a reason that I cannot quite understand.It sometimes leads to version conflict error and the message is not indexed in elasticsearch
This error can happen if the version provided by the connector is lower than the version of the document with the same
_id
in Elasticsearch. When this happens, this means the record offset in Kafka was lower than the a previous record generating the same_id
. This situation is possible if the Kafka topic has multiple partitions, if partitions are created on the fly or if the partitions are deleted and are created again. In my case it happens quite often and it affects the connector performance.The connector should have a new boolean parameter called
version.ignore
. When true, the connector would not attempt to add a version to the document under any circumstances. When false (default), the current behavior would take place.The new config
Its usage
I built a new version this way and it works fine. How can I create a pull request?
The text was updated successfully, but these errors were encountered: