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.

Sign up for GitHub

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

Jump to bottom

Support for "resume" offset? #78

Closed
gengel opened this issue May 14, 2018 · 2 comments
Closed

Support for "resume" offset? #78

gengel opened this issue May 14, 2018 · 2 comments

Comments

@gengel
Copy link

gengel commented May 14, 2018

Since kt sets a consumer group id, it should be possible to simply start reading from a given TopicPartition based on the offset where it stopped reading the last time it was run for that username? (Assuming that kt commits offsets as it reads)

Something like kt consume -offsets all=resume would be handy.
fgeller added a commit that referenced this issue Jun 20, 2018
@fgeller
consume: starts work on resume for #78.
a5146e6
fgeller added a commit that referenced this issue Oct 28, 2018
@fgeller
consume: adds group arg to mark offsets for.
95ac2b7 
should enable resuming offsets as well #78
fgeller added a commit that referenced this issue Oct 30, 2018
@fgeller
consume: first stab at resume #78
79e1b73
@fgeller fgeller mentioned this issue Oct 30, 2018
Merged
fgeller added a commit that referenced this issue Oct 30, 2018
@fgeller
consume: test for resume. fix #78
2754c21
@fgeller
Copy link
Owner

fgeller commented Oct 30, 2018

@gengel sorry for the delay - but i just pushed a version that supports a resume keyword, similar to newest and oldest. use go get -u github.com/fgeller/kt if you want to test it now, or let me know - it might be a couple of days before i package a release.

@gengel
Copy link
Author

gengel commented Oct 30, 2018

Woohoo, this is wonderful news!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fgeller @gengel