Thanks, that helps! We are using the new consumer, but we aren't sure yet whether it will be easier in our case to reset the offsets directly in the consumers or do it externally, so we wanted to experiment with both.
-Jack On Tue, Nov 24, 2015 at 7:18 PM Jason Gustafson <ja...@confluent.io> wrote: > The consumer metadata request was renamed to group coordinator request > since the coordinator plays a larger role in 0.9 for managing groups, but > its protocol format is exactly the same on the wire. > > As Gwen suggested, I would recommend trying the new consumer API which > saves the trouble of accessing the request API directly. > > -Jason > > On Tue, Nov 24, 2015 at 2:56 PM, Gwen Shapira <g...@confluent.io> wrote: > > > Are you using the new consumer API (KafkaConsumer) or the older > > ZookeeperConnector? > > > > KafkaConsumer has seek() API allowing you to replay events from any > point. > > You can also manually commit a specific offset. > > > > Gwen > > > > On Tue, Nov 24, 2015 at 2:11 PM, Jack Lund < > > jack.l...@braintreepayments.com> > > wrote: > > > > > We’re running Kafka 0.9.0, and storing our offsets in Kafka. We need a > > way > > > to reset the offsets for a consumer so that we can replay the stream. > We > > > looked at this wiki page: > > > > > > > > > https://cwiki.apache.org/confluence/display/KAFKA/Committing+and+fetching+consumer+offsets+in+Kafka > > > , > > > but the code doesn’t seem to be valid any more (for instance, > > > kafka.javaapi.ConsumerMetadataRequest and Response don’t seem to exist > > any > > > more). > > > > > > Is there any updated code snippets for fetching/committing offsets in > > > Kafka? > > > > > > Thanks > > > > > > -Jack Lund > > > Braintree Payments > > > > > > > > >
