[ https://issues.apache.org/jira/browse/FLINK-27137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519534#comment-17519534 ]
dengziming commented on FLINK-27137: ------------------------------------ In fact, AdminClient is better when concerning getting offsets, for example, AdminClient supports max-timestamp whereas KafkaConsumer doesn't, and KafkaConsumer contains extra component, for example `Fetcher` and `ConsumerCoordinator`. > 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)