[
https://issues.apache.org/jira/browse/KAFKA-2982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15052947#comment-15052947
]
Ismael Juma commented on KAFKA-2982:
------------------------------------
I think this is a big enough change that we should discuss it in the mailing
list. Once we deprecate those classes, users will have a bunch of warnings in
their builds. My take is that it's probably OK to deprecate the old producer,
but too soon to deprecate the old consumers.
The reason is that we had a full release cycle where the new producer was
considered production-ready whereas the new consumer is still marked as beta in
the documentation and annotated with `Unstable`. I think we can only deprecate
the old consumer once we consider the new consumer production-ready. And, if we
follow the same model as the producer, it may even take longer than that.
> Mark the old Scala producer and consumer clients and related classes as
> deprecated
> ----------------------------------------------------------------------------------
>
> Key: KAFKA-2982
> URL: https://issues.apache.org/jira/browse/KAFKA-2982
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Grant Henke
> Assignee: Grant Henke
>
> Now that the new producer and consumer are released the old Scala producer
> and consumer clients should be deprecated to encourage use of the new clients
> and facilitate the removal of the old clients.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
