Agreed that it has been partially discussed in the thread "[jira] [Updated] (KAFKA-1046) Added support for Scala 2.10 builds while maintaining compatibility with 2.8.x" with the discussion being that it's not a good idea to apply the same path to 0.8-beta1-candidate branch. However, I am more looking for advice on how stable the 0.8 branch is to be fit for deployment in production.
On 24 September 2013 18:55, Neha Narkhede <neha.narkh...@gmail.com> wrote: > This was discussed before - > http://mail-archives.apache.org/mod_mbox/kafka-users/201309.mbox/browser > > Thanks, > Neha > On Sep 23, 2013 11:43 PM, "Aniket Bhatnagar" <aniket.bhatna...@gmail.com> > wrote: > > > We are looking to adopt Kafka for our in stream processing use case. One > of > > the issue seems to be that we use scala 2.10.2 however the the 0.8 Beta1 > > release does not seem to support scala 2.10.x. As a result, we are not > able > > to use Kafka Scala client. I was wondering if we can use branch 0.8 which > > seems to have the patch KAFKA-1046 incorporated. But I am not sure, if > > branch 0.8 is considered stable enough for production usage. I tried to > do > > a diff of branches 0.8 and -0.8.0-beta1-candidate1 and there seems to be > a > > lot of changes between the branches (about 193 different files). Any > > insight on this would be very helpful. > > > > Also, the other option is to build client jar (essentially core jar) from > > 0.8 branch and deploy 0.8 Beta1 release on server. Is that recommended? > > >
