You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
Closesredpanda-data#4073.
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.
The text was updated successfully, but these errors were encountered: