-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Offset metadata should not be lost in case of batch reprocessing #2252
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
Milestone
Comments
frosiere
added a commit
to frosiere/spring-kafka
that referenced
this issue
May 3, 2022
frosiere
added a commit
to frosiere/spring-kafka
that referenced
this issue
May 3, 2022
frosiere
added a commit
to frosiere/spring-kafka
that referenced
this issue
May 4, 2022
frosiere
added a commit
to frosiere/spring-kafka
that referenced
this issue
May 5, 2022
garyrussell
pushed a commit
that referenced
this issue
May 9, 2022
garyrussell
pushed a commit
that referenced
this issue
May 9, 2022
garyrussell
pushed a commit
that referenced
this issue
May 9, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue #2170 introduced a way to control the metadata associated to an offset but in case of exception during the processing of a batch, these metadata are no present anymore when records are reprocessed.
So, in this issue, we will ensure these metadata are not lost in such a case.
Javadoc of OffsetAndMetadataProvider has also been reviewed as this provider is used for both, sync and async commits.
The text was updated successfully, but these errors were encountered: