Mailing-List: contact users-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@kafka.apache.org
Received-SPF: pass (nike.apache.org: domain of neha.narkhede@gmail.com
 designates 209.85.212.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAG2rwuOE7dXAn33B0349jdBmg0A29=98JMMBowwXqo_Zv6iEGg@mail.gmail.com>
References: 
 <CAG2rwuOE7dXAn33B0349jdBmg0A29=98JMMBowwXqo_Zv6iEGg@mail.gmail.com>
Date: Tue, 17 Jun 2014 15:06:35 -0700
Message-ID: 
 <CAOG_4QY8R9dXYXUzyGtUcAq8BdDnS4cXyA9qgs=Ov2A6SUU5Ug@mail.gmail.com>
Subject: Re: is it smarter to go with a java class for message
 serialization/des?
From: Neha Narkhede <neha.narkhede@gmail.com>
To: "users@kafka.apache.org" <users@kafka.apache.org>
Content-Type: multipart/alternative; boundary=f46d0438933b6e04f304fc0f5bf8

--f46d0438933b6e04f304fc0f5bf8
Content-Type: text/plain; charset=UTF-8

Yes, backwards incompatibility is a problem when using Java/Scala object
serialization. At LinkedIn, we use Avro as the serialization format for
Kafka data.

Thanks,
Neha


On Tue, Jun 17, 2014 at 11:58 AM, S Ahmed <sahmed1020@gmail.com> wrote:

> My app is in scala and a quick search on serializing a scala class seems to
> have potential issues with different versions of scala (I could be wrong as
> I did a quick search).
>
> Is it generally just a better idea to use plain old java classes for kafka
> messages?
>
> i.e. I simply use jackson like:
>
> public class User implements Serializable {
> ...
> }
>
> // kakfa
> val it = stream.iterator()
> while (it.hasNext()) {
>   val messageAndTopic = it.next
>
>   val user = mapper.readValue(messageAndTopic.message(), classOf[User])
>

--f46d0438933b6e04f304fc0f5bf8--