[
https://issues.apache.org/jira/browse/FLINK-27137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519514#comment-17519514
]
Arvid Heise commented on FLINK-27137:
-------------------------------------
Can you please elaborate on {{In some environments using the AdminClient can be
problematic even if we are not using certaing features.}}
There are some pros to using the AdminClient and the drawbacks have not been
clearly stated, so I'd be inclined to close this ticket with "Won't Do".
After you have stated your concerns clearly, I'd probably go for a hybrid
approach, where a newly introduced {{OffsetRetriever}} abstracts from the used
client to serve both use cases.
> 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: Critical
>
> 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)
