Thanks Grant. On Tue, Feb 23, 2016 at 8:44 AM, Grant Henke <ghe...@cloudera.com> wrote:
> +1 > > I had a jira tracking marking both as deprecated. I agree we should wait to > deprecate the old consumer. I changed the existing jira to be for the > producer and created a new jira to track deprecating the the consumer > sometime in the future (likely in the 0.11 release). > > - KAFKA-2982: Mark the old Scala producer related classes as deprecated > - KAFKA-3264: Mark the old Scala consumer and related classes as > deprecated > > > > > On Mon, Feb 22, 2016 at 11:57 PM, Manikumar Reddy <ku...@nmsworks.co.in> > wrote: > > > +1 > > > > It will be great If we can completely close below issue. > > > > https://issues.apache.org/jira/browse/KAFKA-1843 > > > > > > On Tue, Feb 23, 2016 at 3:25 AM, Joel Koshy <jjkosh...@gmail.com> wrote: > > > > > +1 > > > > > > Thanks for bringing it up > > > > > > On Mon, Feb 22, 2016 at 9:36 AM, Ismael Juma <ism...@juma.me.uk> > wrote: > > > > > > > Hi all, > > > > > > > > The new Java producer was introduced in 0.8.2.0 (released in February > > > > 2015). It has become the default implementation for various tools > since > > > > 0.9.0.0 (released in October 2015) and it is the only implementation > > with > > > > support for the security features introduced in 0.9.0.0. > > > > > > > > Given this, I think there's a good argument for deprecating the old > > Scala > > > > producers for the next release (which is likely to be 0.10.0.0). This > > > would > > > > give our users a stronger signal regarding our plans to focus on the > > new > > > > Java producer going forward. > > > > > > > > Note that this proposal is only about deprecating the old Scala > > producers > > > > as, in my opinion, it is too early to do the same for the old Scala > > > > consumers. > > > > > > > > Thoughts? > > > > > > > > Ismael > > > > > > > > > > > > > -- > Grant Henke > Software Engineer | Cloudera > gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke >
