kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ismael Juma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-5536) Tools splitted between Java and Scala implementation
Date Mon, 10 Jul 2017 16:07:01 GMT

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

Ismael Juma commented on KAFKA-5536:
------------------------------------

Thanks for the PR. Answers to the questions:

1. argparse4j was deemed to be more flexible and chosen for the newer Java tools. It would
probably make sense to use that for all Java tools. But we need to make sure we have tests
to ensure that we don't break compatibility.

2. There are two options for CLI utils:
* If we think it makes sense to share it between tools and core: rewrite in Java in the common
package in the clients module, update Scala code to use it.
* Otherwise: rewrite in Java in the tools module.

> 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)

Mime
View raw message