kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Viktor Somogyi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-5536) Tools splitted between Java and Scala implementation
Date Fri, 07 Jul 2017 12:41:00 GMT

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

Viktor Somogyi commented on KAFKA-5536:
---------------------------------------

I believe the reason (or one of the reasons) for having the clients in java is to avoid the
additional extra scala dependencies. While the brokers are running alone (ideally) on a box,
the clients can be part of a complicated environment, therefore minimalizing the number of
dependencies are desirable.

> 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