[
https://issues.apache.org/jira/browse/FLINK-27137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519919#comment-17519919
]
Gabor Somogyi commented on FLINK-27137:
---------------------------------------
Yep, Kafka community thinks that all offset management MUST be done w/
AdminClient. Majority of the Kafka community agrees that this is a strategic
direction.
Consumers can be used for offset fetching but if any issue arise then they
suggest to switch to AdminClient and not willing to fix Consumer. We've spent
several months on SPARK-32032 to discover all the issues and possibilities...
> Remove usage of AdminClient from KafkaSource logic
> --------------------------------------------------
>
> Key: FLINK-27137
> URL: https://issues.apache.org/jira/browse/FLINK-27137
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Kafka
> Affects Versions: 1.15.0, 1.14.4
> Reporter: Gyula Fora
> Priority: Major
>
> Parts of the KafkaSource logic (specifically the KafkaSourceEnumerator) uses
> the Kafka AdminClient instead of the KafkaConsumer.
> It seems that the KafkaConsumer already provides all the necessary
> information that the enumerator needs so there is no reason for introducing
> the AdminClient.
> In some environments using the AdminClient can be problematic even if we are
> not using certaing features.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
