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

Move fetching last known offset logic to a stand alone function. #177

Merged
merged 2 commits into from
Aug 25, 2014
Merged

Move fetching last known offset logic to a stand alone function. #177

merged 2 commits into from
Aug 25, 2014

Conversation

zackdever
Copy link
Collaborator

The Consumer class fetches the last known offsets in __init__ if
auto_commit is enabled, but it would be nice to expose this behavior
for consumers that aren't using auto commit. This doesn't change
existing behavior, just exposes the ability to easily fetch and set the
last known offsets. Once #162 or something similar lands this may no
longer be necessary, but it looks like that might take a while to make
it through.

@chriso
Copy link

chriso commented Jul 11, 2014

+1 for this feature.

@dpkp dpkp added the consumer label Aug 24, 2014
The `Consumer` class fetches the last known offsets in `__init__` if
`auto_commit` is enabled, but it would be nice to expose this behavior
for consumers that aren't using auto_commit. This doesn't change
existing behavior, just exposes the ability to easily fetch and set the
last known offsets. Once #162 or something similar lands this may no
longer be necessary, but it looks like that might take a while to make
it through.
dpkp added a commit that referenced this pull request Aug 25, 2014
Move fetching last known offset logic to a stand alone function.
@dpkp dpkp merged commit a160361 into dpkp:master Aug 25, 2014
@zackdever zackdever deleted the fetch-last-known-offsets branch September 2, 2014 00:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants