[
https://issues.apache.org/jira/browse/KAFKA-6791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17197411#comment-17197411
]
Jeff Widman commented on KAFKA-6791:
------------------------------------
Should this be closed as "wontfix"?
The associated PR was closed w/o merge with the note
https://github.com/apache/kafka/pull/4902#issuecomment-390830255:
> Closed this PR since it was already fixed by KAFKA-6299.
> Add a CoordinatorNodeProvider in KafkaAdminClient
> -------------------------------------------------
>
> Key: KAFKA-6791
> URL: https://issues.apache.org/jira/browse/KAFKA-6791
> Project: Kafka
> Issue Type: Improvement
> Components: admin
> Reporter: Guozhang Wang
> Assignee: huxihx
> Priority: Major
>
> As we add more and more coordinator-related requests to the admin client, we
> can consider adding a CoordinatorNodeProvider to consolidate the common logic
> pattern of finding the coordinator first, then send the corresponding request.
> Note that 1) with this provider interface it is almost not possible to batch
> multiple groupIds per coordinator; there has to be a little more refactoring
> to make it work. 2) for some requests like list consumers, group ids are not
> known beforehand and hence we cannot use this provider as well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
