cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3188) cqlsh 2.0
Date Sat, 29 Oct 2011 23:51:32 GMT

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

Eric Evans commented on CASSANDRA-3188:
---------------------------------------

bq. I'd like cqlsh in the C* tree, but I'm totally fine with saying "to run this, easy_install
cassandra-dbapi." If you want to get fancy, we can even print that on an import exception.

For curiosity sake, why is that?  Is it just to make it obvious what we expect people to use?
                
> 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.2
>
>         Attachments: 3188.patch4.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

        

Mime
View raw message