Hi Nicolas,
Sorry for the confusion made, there is no communication between clients. We
are in need of using two Kafka client wrappers provided by two external
teams.

Team A has its own Kafka cluster with own client to produce/consume data,
and team B also have their own cluster and clients.

One team (say team A) using Kafka-clients-2.4.0.jar in their wrapper and
another team(say team b) using Kafka-clients-0.10.0.1.jar in their wrapper.

Sample Case:
If we try to produce data with the given wrapper of Team B we got below
exception
!Exception in thread "main" java.lang.NoSuchMethodError:
org.apache.kafka.common.record.Record.recordSize([B[B)I


Thanks and regards,
Gowtham S, MCA



On Wed, 15 Apr 2020 at 19:32, Nicolas Carlot <nicolas.car...@chronopost.fr>
wrote:

> What do you mean by communication between Kafka Clients ?
> A Client is either a producer or a consumer, they don't "communicate"... ?
>
> Le mar. 7 avr. 2020 à 09:01, Gowtham S <gowtham.co....@gmail.com> a écrit
> :
>
> > Hello,
> >
> > As per our team requirements, we are supposed to use and communicate
> > between two different Kafka Clients, provided and managed by two separate
> > teams). Mentioned below are the client versions
> >
> > Version 1 - kafka-clients-2.4.0.jar
> > Version 2 - kafka-clients-0.10.0.1.jar
> >
> > Please suggest if possible to use them without compatibility issues. Is
> it
> > necessary to move the topics to a single Kafka?
> > If necessary to upgrade the clients, suggest the best practices for the
> > same.
> >
> >
> > With regards,
> > Gowtham S, MCA
> >
>
>
> --
> *Nicolas Carlot*
>
> Lead dev
> |  | nicolas.car...@chronopost.fr
>
>
> *Veuillez noter qu'à partir du 20 mai, le siège Chronopost déménage. La
> nouvelle adresse est : 3 boulevard Romain Rolland 75014 Paris*
>
> [image: Logo Chronopost]
> | chronopost.fr <http://www.chronopost.fr/>
> Suivez nous sur Facebook <https://fr-fr.facebook.com/chronopost> et
> Twitter
> <https://twitter.com/chronopost>.
>
> [image: DPD Group]
>

Reply via email to