[
https://issues.apache.org/jira/browse/KAFKA-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14218157#comment-14218157
]
Joe Stein commented on KAFKA-1774:
----------------------------------
some thoughts
1) I think that /clients make sense since this is an admin client.
2) JLine I have heard good things but no personal experience with issues on it
3) If we do this in Java then we won't have the issue with Scala binaries and
client use and easier for java interactions, not sure how much that will matter
in this case though since scripts will just use the CLI and not even care what
it is in.... If we do it in Scala then my answer for #1 might change or we have
to just put scala code in that directory which may not make sense. My
preference is Scala over Java.
4) We have talked about that in
https://issues.apache.org/jira/browse/KAFKA-1595 some, we should drive
consistency if we can. I have had really good experience with
http://wiki.fasterxml.com/JacksonHome in both Java and Scala
> REPL and Shell Client for Admin Message RQ/RP
> ---------------------------------------------
>
> Key: KAFKA-1774
> URL: https://issues.apache.org/jira/browse/KAFKA-1774
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Joe Stein
> Assignee: Andrii Biletskyi
> Fix For: 0.8.3
>
>
> We should have a REPL we can work in and execute the commands with the
> arguments. With this we can do:
> ./kafka.sh --shell
> kafka>attach cluster -b localhost:9092;
> kafka>describe topic sampleTopicNameForExample;
> the command line version can work like it does now so folks don't have to
> re-write all of their tooling.
> kafka.sh --topics --everything the same like kafka-topics.sh is
> kafka.sh --reassign --everything the same like kafka-reassign-partitions.sh
> is
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
