Re: Trunk backwards compatibility (producer / consumer client questions)

2014-08-29 Thread Jun Rao
Yes, the new producer in trunk is compatible with 0.8.1.1 broker. In trunk, we have evolved the format of OffsetCommitRequest, which is used by the old consumer (and will be used by the new consumer). So, to use the consumer in trunk, you will need to upgrade the broker first. Thanks, Jun On Fr

Re: Trunk backwards compatibility (producer / consumer client questions)

2014-08-29 Thread Jay Kreps
Yes, the protocol for metadata, fetch, and produce is the same across both clients and all 0.8.x versions. -Jay On Fri, Aug 29, 2014 at 10:09 AM, Jonathan Weeks wrote: > Thanks, Jay. Follow-up questions: > > Some of our services will produce and consume. Is there consumer code on > trunk that i

Re: Trunk backwards compatibility (producer / consumer client questions)

2014-08-29 Thread Joel Koshy
I think Jun was referring to "consumer" clients. The new producer is compatible with existing brokers. However the new consumer requires a server-side consumer coordinator. On Fri, Aug 29, 2014 at 10:37:12AM -0700, Jonathan Weeks wrote: > Hi Jun, > > Jay indicated that the new producer client on

Re: Trunk backwards compatibility (producer / consumer client questions)

2014-08-29 Thread Jonathan Weeks
Hi Jun, Jay indicated that the new producer client on trunk is backwards compatible with 0.8.1.1 (see thread below) — can you elaborate? Given the consumer re-write for 0.9, I can definitely see how that would break backwards compatibility, but Jay indicates that the producer on the trunk will

Re: Trunk backwards compatibility (producer / consumer client questions)

2014-08-29 Thread Jun Rao
The old clients with be compatible with the new broker. However, in order to use the new clients, you will need to upgrade to the new broker first. Thanks, Jun On Fri, Aug 29, 2014 at 10:09 AM, Jonathan Weeks wrote: > Thanks, Jay. Follow-up questions: > > Some of our services will produce and