kafka-jira mailing list archives

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

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

Paolo Patierno commented on KAFKA-5536:
---------------------------------------

Thanks Ismael !

1. Good. I can recover the previous work I have done using argparse4j. In any case my idea
is to mimic the same behaviour we have with the joptsimple lib in order to avoid problems.
2. Regarding sharing the code, the CommandLineUtils leverages on the joptsimple lib so it's
not possible just move it to use argparse4j in Java and then sharing with other Scala tools
(even because the migration will be slow, tool by tool and not all together). So it seems
that the better solution for now is just rewriting for the tools module.

Let's see how things will evolve on TopicCommand, the first tool that will be the subject
of this big migration.

> 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