cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3188) cqlsh 2.0
Date Tue, 13 Sep 2011 20:19:09 GMT

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

Jonathan Ellis commented on CASSANDRA-3188:
-------------------------------------------

bq. Would it address the concerns of CASSANDRA-3010 if we built the Windows releases with
py2exe or something like it?

I think the concerns there are (1) Windows, and py2exe would be great, and (2) anywhere else
that building Thrift or other prerequisites is a bitch.

But I think (2) is mostly taken care of by pypi now, so yeah, if Python makes more sense as
an implementation language then let's go for it.

> 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

        

Mime
View raw message