-
Notifications
You must be signed in to change notification settings - Fork 483
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
-o when consuming from multiple partitions? #7
Comments
It applies to all of the partitions, which is highly impractical if it werent for the symbolic offsets:
|
So, it doesn’t work with manually entered offsets? Or, how does stored work with kafkacat? Is there a way to tell it to store and read offsets in a directory (like kafkatee?) On Oct 16, 2014, at 12:18 PM, Magnus Edenhill notifications@github.com wrote:
|
It doesnt work with absolute offsets, no, or.. it works in the way that it'll use that offset for all partitions ,which is probably wrong. Use I'm guessing you want something like:
right? |
Ah! offset.store.path will work just fine, I think. Just tested this and I think it works. Question, if I use -e, or -c , will the offset files be written to when kafkacat exits? Or will they only be written to every auto.commit.interval.ms? On Oct 16, 2014, at 1:07 PM, Magnus Edenhill notifications@github.com wrote:
|
Both, every commit.interval.ms and at shutdown. |
What happens if SIGINT (ctrl-C?) |
It will exit cleanly (and commit). |
Huhm, maybe it wont, it will destroy rdkafka but doesnt wait for completion. I should fix that. |
Do you desire the per-partition -o offset switch? |
No, I don’t think so… That might be useful for debugging now and then, but the stored offset files should do just fine. On Oct 17, 2014, at 3:27 AM, Magnus Edenhill notifications@github.com wrote:
|
I think I asked this before, but I don't remember the answer.
When consuming from multiple partitions, what does the
-o <offset>
flag do? Offsets are for particular partitions. Which partition's offset is-o
referring to?The text was updated successfully, but these errors were encountered: