>From my point of view, it seems very odd to deprecate the Scala producer but
>not the consumer. So, I would vote to deprecate them both in 0.10.
It doesn't sound like there's an established mechanism for deprecation. So, for
the sake of discussion, how about:
* Start with deprecation annotations. It's just a marker that they're now
living on borrowed time.
* Remove the ability to connect from these deprecated clients two releases
later - so I mean 0.12, not 0.10.0.2.
Andrew Schofield
----------------------------------------
> Subject: Re: [DISCUSS] Deprecating the old Scala producers for the next
> release
> From: f...@apache.org
> Date: Tue, 23 Feb 2016 18:46:27 +0000
> To: dev@kafka.apache.org
>
> It does make sense, thanks for the clarification. If we deprecate the
> producer first, does it mean that the following release won't have a scala
> producer but will have a scala consumer? Actually I should have asked this
> question first: what's the deprecation path precisely?
>
> -Flavio
>
>> On 23 Feb 2016, at 17:28, Ismael Juma <ism...@juma.me.uk> wrote:
>>
>> Hi Flavio,
>>
>> On Tue, Feb 23, 2016 at 9:23 AM, Flavio Junqueira <f...@apache.org> wrote:
>>
>>> Ismael, I'm curious about why you want to deprecate one and not the other.
>>> You say that it is premature to deprecate the old scala consumers and I'm
>>> wondering about the reasoning behind it.
>>>
>>
>> The new Java producer was introduced in 0.8.2 and it's considered
>> production-ready. The new Java consumer was introduced in 0.9.0.0 and it's
>> still marked as beta. We would like to have at least one full release cycle
>> where the new consumer is no longer in beta, before we consider deprecating
>> the old consumers. Does that make sense?
>>
>> Ismael
>
