[
https://issues.apache.org/jira/browse/CASSANDRA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
paul cannon updated CASSANDRA-3188:
-----------------------------------
Attachment: 3188.patch1.txt
This doesn't have any awesome help text in it yet, but I'm uploading this to
get some review.
It does have a working ASSUME, DESCRIBE, and SHOW, much (imo) improved controls
for determining where to connect, a config file, much better error handling,
and smarter tab completion in a lot of areas.
Some of the working new commands:
{noformat}
ASSUME mycolumnfam NAMES ARE uuid;
ASSUME mycolumnfam VALUES ARE int;
ASSUME mycolumnfam(somecol) VALUES ARE ascii;
DESCRIBE KEYSPACE foo;
DESCRIBE COLUMNFAMILY bar;
DESCRIBE CLUSTER;
DESCRIBE SCHEMA;
SHOW VERSIONS;
SHOW HOST;
SHOW ASSUMPTIONS;
{noformat}
Downside: the ASSUME stuff all depends on a patch to the python CQL driver. See:
http://code.google.com/a/apache-extras.org/p/cassandra-dbapi2/source/detail?r=d31c412df1a66d0c8b99ba313a19855f1ef8106b&name=override-decoder
The tab completion could still be improved a lot, which I think would greatly
aid usability, together with some good help text.
> 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
>
> Attachments: 3188.patch1.txt
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
