[
https://issues.apache.org/jira/browse/CASSANDRA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13103789#comment-13103789
]
paul cannon commented on CASSANDRA-3188:
----------------------------------------
For the sake of the potential set of features, I'd lean heavily toward Python
on this one: much more easily integrated with readline (when available) and
curses-type capabilities in general, plus more flexible/powerful in parsing
input, formatting output, and responding to error situations.
Would it address the concerns of CASSANDRA-3010 if we built the Windows
releases with py2exe or something like it? You'd just get a clicky or
command-line executable, no manual Python or Thrift installing to worry about.
..On the other hand, cassandra-cli uses JMX for a few of its cluster-inspection
duties; are those things that might be important in cqlsh 2.0? Guess I should
find out what they are.
> cqlsh 2.0
> ---------
>
> Key: CASSANDRA-3188
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3188
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jonathan Ellis
> Assignee: paul cannon
> Fix For: 1.0.1
>
>
> I'd like to see some improvements to cqlsh to bring it to feature parity w/
> the old cli:
> - describe [<KS> | <CF> | cluster | schema]
> - assume
> - connect / don't crap out w/ stacktrace if C* isn't currently running on
> localhost
> - help
> It may be easier to do this by forking the cli and replacing its one-off api
> with CQL, or it may be easier to add these features to cqlsh.
> Either is fine, but if it's a close call my inclination would be to build it
> in Java for the reasoning over on CASSANDRA-3010.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
