You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Paolo Patierno (JIRA)" <ji...@apache.org> on 2017/07/07 13:01:00 UTC

[jira] [Comment Edited] (KAFKA-5536) Tools splitted between Java and Scala implementation

    [ https://issues.apache.org/jira/browse/KAFKA-5536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078032#comment-16078032 ] 

Paolo Patierno edited comment on KAFKA-5536 at 7/7/17 1:00 PM:
---------------------------------------------------------------

[~ijuma] yes it makes totally sense to me ! For this reason, referring to this JIRA https://issues.apache.org/jira/browse/KAFKA-5561 I'm working on re-rewriting the TopicCommand tool in Java using the AdminClient :-)
Hoping it's ok for you.

Thanks !


was (Author: ppatierno):
[~ijuma] yes it makes totally sense to me ! For this reason, referring to this JIRA https://issues.apache.org/jira/browse/KAFKA-5561 I'm working on re-rewriting the TopicCommand tool in Java using the AdminClient :-)

Thanks !

> Tools splitted between Java and Scala implementation
> ----------------------------------------------------
>
>                 Key: KAFKA-5536
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5536
>             Project: Kafka
>          Issue Type: Wish
>            Reporter: Paolo Patierno
>
> Hi,
> is there any specific reason why tools are splitted between Java and Scala implementations ?
> Maybe it could be better having only one language for all of them.
> What do you think ?
> Thanks,
> Paolo



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)