My understanding is that ideally the 0.8.3 consumer should work with an 0.8.2 broker if the offset commit config was set to "zookeeper".
The only thing that might not work is offset commit to Kafka, which makes sense since the 0.8.2 broker does not support Kafka based offset management. If we broke all kinds of offset commits, then it seems like a regression, no? On Thu, Apr 23, 2015 at 7:26 PM, Gwen Shapira <gshap...@cloudera.com> wrote: > I didn't think 0.8.3 consumer will ever be able to talk to 0.8.2 > broker... there are some essential pieces that are missing in 0.8.2 > (Coordinator, Heartbeat, etc). > Maybe I'm missing something. It will be nice if this will work :) > > Mind sharing what / how you tested? Were there no errors in broker > logs after your fix? > > On Thu, Apr 23, 2015 at 5:37 PM, Sean Lydon <lydon.s...@gmail.com> wrote: > > Currently the clients consumer (trunk) sends offset commit requests of > > version 2. The 0.8.2 brokers fail to handle this particular request > > with a: > > > > java.lang.AssertionError: assertion failed: Version 2 is invalid for > > OffsetCommitRequest. Valid versions are 0 or 1. > > > > I was able to make this work via a forceful downgrade of this > > particular request, but I would like some feedback on whether a > > "enable.commit.downgrade" configuration would be a tolerable method to > > allow 0.8.3 consumers to interact with 0.8.2 brokers. I'm also > > interested in this even being a goal worth pursuing. > > > > Thanks, > > Sean > -- Thanks, Neha
