-
Notifications
You must be signed in to change notification settings - Fork 36
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
feat: add timestamp-query
feature to allow timestamp offset query
#248
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.
It's definitely a feature that we should support, but it needs a bit more thorough API design (see code-attached comment) and a test.
I have change the code for a better API with |
Sorry for the long wait. I have added test to query timestamp offset. @crepererum |
Pls have a look. @crepererum |
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.
Thanks for addressing all the nitpicks and providing a very clean PR. Good job!
Ah, last minute issue: could you squash all commits into a single one and name it:
|
done |
Sorry for the CI failure, this will get fixed by #251 (seems to be bad timing). |
@crepererum seems good now. |
This commit allow timestamp query for partition offset. As stated in the doc comment of
OffsetAt
, timestamp-based query is inconsistent, but I think it better to let the users make their own choice instead of total removal of this sometimes useful feature. I add a feature gate to disable timestamp-based query for offset by default, only those actively looking for timestamp-based query would enable this feature.