[
https://issues.apache.org/jira/browse/KAFKA-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080159#comment-16080159
]
ASF GitHub Bot commented on KAFKA-5561:
---------------------------------------
GitHub user ppatierno opened a pull request:
https://github.com/apache/kafka/pull/3514
KAFKA-5561: Rewrite TopicCommand using the new Admin client (** WIP do not
merge **)
Start on porting TopicCommand from Scala to Java using Admin Client API as
well
Please do not merge it's just for evaluation with other contributors and
committers as starting point for a migration from Scala to Java for tools.
Other considerations here :
https://issues.apache.org/jira/browse/KAFKA-5536
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ppatierno/kafka kafka-5561
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/3514.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3514
----
commit a4146eeab9960d183733bc195516839fc2f76601
Author: ppatierno <ppatie...@live.com>
Date: 2017-07-10T10:51:53Z
Start on porting TopicCommand from Scala to Java using Admin Client API as
well
----
> Rewrite TopicCommand using the new Admin client
> -----------------------------------------------
>
> Key: KAFKA-5561
> URL: https://issues.apache.org/jira/browse/KAFKA-5561
> Project: Kafka
> Issue Type: Improvement
> Components: tools
> Reporter: Paolo Patierno
> Assignee: Paolo Patierno
>
> Hi,
> as suggested in the https://issues.apache.org/jira/browse/KAFKA-3331, it
> could be great to have the TopicCommand using the new Admin client instead of
> the way it works today.
> As pushed by [~gwenshap] in the above JIRA, I'm going to work on it.
> Thanks,
> Paolo
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
