You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Matthias J. Sax (JIRA)" <ji...@apache.org> on 2019/02/17 19:02:00 UTC
[jira] [Commented] (KAFKA-5601) Refactor ReassignPartitionsCommand
to use AdminClient
[ https://issues.apache.org/jira/browse/KAFKA-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16770541#comment-16770541 ]
Matthias J. Sax commented on KAFKA-5601:
----------------------------------------
Moving all major/minor/trivial tickets that are not merged yet out of 2.2 release.
> Refactor ReassignPartitionsCommand to use AdminClient
> -----------------------------------------------------
>
> Key: KAFKA-5601
> URL: https://issues.apache.org/jira/browse/KAFKA-5601
> Project: Kafka
> Issue Type: Improvement
> Reporter: Tom Bentley
> Assignee: Tom Bentley
> Priority: Major
> Labels: kip
> Fix For: 2.2.0
>
>
> Currently the {{ReassignPartitionsCommand}} (used by {{kafka-reassign-partitions.sh}}) talks directly to ZooKeeper. It would be better to have it use the AdminClient API instead.
> This would entail creating two new protocol APIs, one to initiate the request and another to request the status of an in-progress reassignment. As such this would require a KIP.
> This touches on the work of KIP-166, but that proposes to use the {{ReassignPartitionsCommand}} API, so should not be affected so long as that API is maintained.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)