[
https://issues.apache.org/jira/browse/FLINK-27137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519476#comment-17519476
]
Gyula Fora edited comment on FLINK-27137 at 4/8/22 9:56 AM:
------------------------------------------------------------
I was not aware of that [~martijnvisser] but I think it still probably make
sense to remove the AdminClient. Basically the logic for using it seems to be
that we might use some features in the future that the consumer might not have
at that type :)
was (Author: gyfora):
I was not aware of that [~martijnvisser] but I think it still might make sense
to remove the AdminClient. Basically the logic for using it seems to be that we
might use some features in the future that the consumer might not have at that
type :)
> 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)
