Skip to content
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

[BUG] seekTo throws NPE when no offset found for a timestamp #631

Closed
authorjapps opened this issue Feb 28, 2024 · 0 comments · Fixed by #630
Closed

[BUG] seekTo throws NPE when no offset found for a timestamp #631

authorjapps opened this issue Feb 28, 2024 · 0 comments · Fixed by #630

Comments

@authorjapps
Copy link
Owner

authorjapps commented Feb 28, 2024

@a1shadows, Now you have been added as a collaborator, can you please Click here- accept and join ?


reported by @a1shadows :

(1)
If there are partitions for which there is no valid offset corresponding to the timestamp to seek to, the offsetForTimestamp method still includes it in the Map returned, but with a NULL value. We need to skip all partitions that have offset as NULL when subscribing to avoid an error when we try to seek to the offset at a later step.


(2)
There was a bug in the seekTo feature . In situations where there are multiple partitions on the topic and some of the partitions do not have a valid offset corresponding the timestamp to seek to, the seek operation will give an NPE.


More discussions are here:
#630 (comment)

@authorjapps authorjapps mentioned this issue Feb 28, 2024
12 tasks
@authorjapps authorjapps added this to the BELGIUM-MINOR-RELEASE milestone Mar 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant