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

rpk: make it possible to consume messages using timestamps #4073

Closed
rkruze opened this issue Mar 22, 2022 · 0 comments · Fixed by #4091
Closed

rpk: make it possible to consume messages using timestamps #4073

rkruze opened this issue Mar 22, 2022 · 0 comments · Fixed by #4091
Labels
area/rpk kind/enhance New feature or request

Comments

@rkruze
Copy link
Contributor

rkruze commented Mar 22, 2022

Who is this for and what problem do they have today?

Currently, it isn't possible to consume messages using rpk between given timestamps. You can do this today with kcat using something like the following: kcat -b mybroker -C -t mytopic -o s@1568276612443 -o e@1568276617901 we should have something similar in rpk.

What are the success criteria?

Be able to consume messages between given offsets.

Why is solving this problem impactful?

Allows for users who want messages between a given time period.

@rkruze rkruze added kind/enhance New feature or request area/rpk labels Mar 22, 2022
andrewhsu pushed a commit to andrewhsu/redpanda that referenced this issue Mar 25, 2022
We now:

- can consume through the end and quit
- can consume based on time
- have many options for representing time ranges and durations

Previously, consuming to an end offset left the client running in the
paranoid case that a new partition could be discovered and consumed to
that end offset. Now, we take a snapshot of the end offsets when rpk
starts, consume to those, and quit.

Closes redpanda-data#4073.
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/rpk kind/enhance New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant