Hi,
The responses in this thread were positive, but there weren't many. A few
months passed and Sriharsha encouraged me to reopen the thread given that
the 2.9 build has been broken for at least a week[1] and no-one seemed to
notice.
Do we want to invest more time so that the 2.9 build continues
+1 for dropping 2.9
On Wed, Jul 8, 2015 at 9:15 AM, Sriharsha Chintalapani ka...@harsha.io
wrote:
I am +1 on dropping 2.9.x support.
Thanks,
Harsha
On July 8, 2015 at 7:08:12 AM, Ismael Juma (mli...@juma.me.uk) wrote:
Hi,
The responses in this thread were positive, but there weren't
I am +1 on dropping 2.9.x support.
Thanks,
Harsha
On July 8, 2015 at 7:08:12 AM, Ismael Juma (mli...@juma.me.uk) wrote:
Hi,
The responses in this thread were positive, but there weren't many. A few
months passed and Sriharsha encouraged me to reopen the thread given that
the 2.9 build
+1.
Scala 2.9 has been 4 years old and I think it is time to drop it.
On Wed, Jul 8, 2015 at 7:22 AM, Grant Henke ghe...@cloudera.com wrote:
+1 for dropping 2.9
On Wed, Jul 8, 2015 at 9:15 AM, Sriharsha Chintalapani ka...@harsha.io
wrote:
I am +1 on dropping 2.9.x support.
Thanks,
+1
On Wed, Jul 8, 2015 at 9:52 AM, Guozhang Wang wangg...@gmail.com wrote:
+1.
Scala 2.9 has been 4 years old and I think it is time to drop it.
On Wed, Jul 8, 2015 at 7:22 AM, Grant Henke ghe...@cloudera.com wrote:
+1 for dropping 2.9
On Wed, Jul 8, 2015 at 9:15 AM, Sriharsha
We should consider deprecating the scala API so scala version doesn't even
matter anymore for folks... we could even pin the broker to a specific
Scala version too
Of course this makes sense for the Java produce but maybe not just yet for
the consumer, maybe 0.9.0.
Not having to build in
+1 for dropping 2.9.x support
Kind regards,
Stevo Slavic.
On Fri, Mar 27, 2015 at 3:20 PM, Ismael Juma mli...@juma.me.uk wrote:
Hi all,
The Kafka build currently includes support for Scala 2.9, which means that
it cannot take advantage of features introduced in Scala 2.10 or depend on
Hi all,
The Kafka build currently includes support for Scala 2.9, which means that
it cannot take advantage of features introduced in Scala 2.10 or depend on
libraries that require it.
This restricts the solutions available while trying to solve existing
issues. I was browsing JIRA looking for
+1. But can we also look at this from the deployment base point view and
find out how many production deployments are still using 2.9? If there is
not any, dropping it is really an easy decision.
Thanks
Sent from my iPhone
On Mar 27, 2015, at 8:21 AM, Ismael Juma mli...@juma.me.uk wrote:
Hi
