You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@kafka.apache.org by "M. Manna" <ma...@gmail.com> on 2019/09/19 12:58:16 UTC
Question on Kafka Client Upgrade
Hello,
Does it matter if we upgrade the client jar from 2.1.0 to 2.3.0 - but the
brokers are using 2.2.0?
https://kafka.apache.org/23/documentation/streams/upgrade-guide
We don't use streams, just plain producer/consumer clients. For us, would
it matter at all?
Thanks,
Re: Question on Kafka Client Upgrade
Posted by "M. Manna" <ma...@gmail.com>.
Wow totally missed the confluent link - appreciate the response here.
I guess we can somehow create a cwiki page to briefly list this. I’ll start
a thread if possible.
Thanks a bunch...
On Fri, 20 Sep 2019 at 09:42, Karolis Pocius
<ka...@sentiance.com.invalid> wrote:
> That should not be a problem as java clients support bidirectional
> compatibility. See
>
> https://www.confluent.io/blog/upgrading-apache-kafka-clients-just-got-easier/
>
> The “bidirectional” client compatibility work done in KIP-35
> > <
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-35+-+Retrieving+protocol+version
> >
> > and KIP-97
> > <
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-97%3A+Improved+Kafka+Client+RPC+Compatibility+Policy
> >
> > removed these limitations. New Java clients can now communicate with old
> > brokers. The Confluent source-available clients for C, C++, and other
> > languages no longer need to be reconfigured when the broker version
> > changes. You can now upgrade the client whenever you want to get access
> to
> > new features or bug fixes, without worrying about the broker version.
> >
>
> On Thu, Sep 19, 2019 at 3:58 PM M. Manna <ma...@gmail.com> wrote:
>
> > Hello,
> >
> > Does it matter if we upgrade the client jar from 2.1.0 to 2.3.0 - but the
> > brokers are using 2.2.0?
> >
> > https://kafka.apache.org/23/documentation/streams/upgrade-guide
> >
> > We don't use streams, just plain producer/consumer clients. For us, would
> > it matter at all?
> >
> > Thanks,
> >
>
Re: Question on Kafka Client Upgrade
Posted by Karolis Pocius <ka...@sentiance.com.INVALID>.
That should not be a problem as java clients support bidirectional
compatibility. See
https://www.confluent.io/blog/upgrading-apache-kafka-clients-just-got-easier/
The “bidirectional” client compatibility work done in KIP-35
> <https://cwiki.apache.org/confluence/display/KAFKA/KIP-35+-+Retrieving+protocol+version>
> and KIP-97
> <https://cwiki.apache.org/confluence/display/KAFKA/KIP-97%3A+Improved+Kafka+Client+RPC+Compatibility+Policy>
> removed these limitations. New Java clients can now communicate with old
> brokers. The Confluent source-available clients for C, C++, and other
> languages no longer need to be reconfigured when the broker version
> changes. You can now upgrade the client whenever you want to get access to
> new features or bug fixes, without worrying about the broker version.
>
On Thu, Sep 19, 2019 at 3:58 PM M. Manna <ma...@gmail.com> wrote:
> Hello,
>
> Does it matter if we upgrade the client jar from 2.1.0 to 2.3.0 - but the
> brokers are using 2.2.0?
>
> https://kafka.apache.org/23/documentation/streams/upgrade-guide
>
> We don't use streams, just plain producer/consumer clients. For us, would
> it matter at all?
>
> Thanks,
>