Done: https://issues.apache.org/jira/browse/KAFKA-12881
On Wed, Jun 2, 2021 at 9:54 PM Ismael Juma wrote:
> Yeah, I think that would make sense regarding point 3.
>
> Ismael
>
> On Wed, Jun 2, 2021 at 12:44 PM Josep Prat
> wrote:
>
> > Hi Ismael,
> >
> > That makes sense then. I guess the rest
Yeah, I think that would make sense regarding point 3.
Ismael
On Wed, Jun 2, 2021 at 12:44 PM Josep Prat
wrote:
> Hi Ismael,
>
> That makes sense then. I guess the rest of the deprecated methods might
> have similar issues like the ones you described. I see some will be covered
> by KAFKA-12588
Hi Ismael,
That makes sense then. I guess the rest of the deprecated methods might
have similar issues like the ones you described. I see some will be covered
by KAFKA-12588.
Thanks for your time explaining the reasoning behind it doesn't make sense
to remove them as of yet. Shall I create a tick
Hi,
1. alterConfigs cannot be removed as there are some cases that are not
possible via the incrementAlterConfigs API, there is a PR where a
discussion is ongoing https://github.com/apache/kafka/pull/10514
2. Consumer.poll(long) has no direct replacement (Consumer.poll(Duration)
has slightly diffe
Hi Ismael,
Thanks for your quick answer.
For example, I've seen the
org.apache.kafka.clients.consumer.Consumer#poll(long) deprecated in KIP-266
(Kafka 2.0.0) and in the same class methods
org.apache.kafka.clients.consumer.Consumer#committed(org.apache.kafka.common.TopicPartition)
and
org.apache.ka
Hi Josep,
We have removed nearly all of the apis we plan to remove for 3.0. The
following JIRA is still in progress:
https://issues.apache.org/jira/browse/KAFKA-12588
Aside from KAFKA-12588, which APIs were you thinking of that could be
removed in 3.0?
Ismael
On Wed, Jun 2, 2021 at 11:52 AM Jo
