You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2011/09/12 23:19:09 UTC
[jira] [Created] (CASSANDRA-3188) cqlsh 2.0
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
[jira] [Updated] (CASSANDRA-3188) cqlsh 2.0
Posted by "paul cannon (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
paul cannon updated CASSANDRA-3188:
-----------------------------------
Attachment: 3188.patch4.txt
Ready to rock
> 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
[jira] [Commented] (CASSANDRA-3188) cqlsh 2.0
Posted by "Jonathan Ellis (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13124334#comment-13124334 ]
Jonathan Ellis commented on CASSANDRA-3188:
-------------------------------------------
"import readline" breaks on Windows
> 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
[jira] [Commented] (CASSANDRA-3188) cqlsh 2.0
Posted by "Eric Evans (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13139058#comment-13139058 ]
Eric Evans commented on CASSANDRA-3188:
---------------------------------------
Wow, this looks nice; Great work Paul!
We should publish the doc on the website (I can do that when it's committed if someone doesn't beat me to it).
Also, since this requires the Python module, will it be going into that tree, or into Cassandra's? Either way, we should probably include some kind of installer.
> 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
[jira] [Commented] (CASSANDRA-3188) cqlsh 2.0
Posted by "Jonathan Ellis (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13137572#comment-13137572 ]
Jonathan Ellis commented on CASSANDRA-3188:
-------------------------------------------
Can you update build.xml to include it in the tarball?
> 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
[jira] [Updated] (CASSANDRA-3188) cqlsh 2.0
Posted by "paul cannon (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
paul cannon updated CASSANDRA-3188:
-----------------------------------
Attachment: 3188.patch3.txt
3188.patch3.txt: Fixes everything I can find which isn't probably an issue with the dbapi2 driver itself.
> 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.patch1.txt, 3188.patch2.txt, 3188.patch3.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
[jira] [Resolved] (CASSANDRA-3188) cqlsh 2.0
Posted by "Jonathan Ellis (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-3188.
---------------------------------------
Resolution: Fixed
Assignee: paul cannon (was: Jonathan Ellis)
added empty file.
> 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.3
>
> Attachments: 3188.patch5.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
[jira] [Commented] (CASSANDRA-3188) cqlsh 2.0
Posted by "Jonathan Ellis (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13125927#comment-13125927 ]
Jonathan Ellis commented on CASSANDRA-3188:
-------------------------------------------
I think dbapi2 users are already living on the bleeding edge enough that we can make them upgrade. :)
> 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
[jira] [Commented] (CASSANDRA-3188) cqlsh 2.0
Posted by "Jonathan Ellis (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13139070#comment-13139070 ]
Jonathan Ellis commented on CASSANDRA-3188:
-------------------------------------------
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.
> 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
[jira] [Updated] (CASSANDRA-3188) cqlsh 2.0
Posted by "paul cannon (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
paul cannon updated CASSANDRA-3188:
-----------------------------------
Attachment: (was: 3188.patch2.txt)
> 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
[jira] [Updated] (CASSANDRA-3188) cqlsh 2.0
Posted by "paul cannon (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
paul cannon updated CASSANDRA-3188:
-----------------------------------
Attachment: (was: 3188.patch4.txt)
> 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.3
>
> Attachments: 3188.patch5.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
[jira] [Commented] (CASSANDRA-3188) cqlsh 2.0
Posted by "paul cannon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13103977#comment-13103977 ]
paul cannon commented on CASSANDRA-3188:
----------------------------------------
I'm super -1 on making mx4j an official dependency, btw. Would not want for it to become the de facto standard for non-java jmx access, when it's really only useful with a browser. Screen scraping sucks. Maybe some more appropriate jmx adapter, though.
> 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
[jira] [Reopened] (CASSANDRA-3188) cqlsh 2.0
Posted by "paul cannon (Reopened) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
paul cannon reopened CASSANDRA-3188:
------------------------------------
Assignee: Jonathan Ellis (was: paul cannon)
Somehow this seems to have been committed without the empty pylib/cqlshlib/__init__.py file. Without that, cqlsh fails to import from the cqlshlib package.
> cqlsh 2.0
> ---------
>
> Key: CASSANDRA-3188
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3188
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Fix For: 1.0.3
>
> Attachments: 3188.patch5.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
[jira] [Commented] (CASSANDRA-3188) cqlsh 2.0
Posted by "Eric Evans (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13139647#comment-13139647 ]
Eric Evans commented on CASSANDRA-3188:
---------------------------------------
bq. Because it's a core part of the distribution, or will be. By analogy, it would feel wrong for psql to be a separate project from postgresql core.
So it sounds like you're saying that we need it to satisfy the "ships with a client shell" requirement. That's fine with me, but brace yourself for the impending criticism that the requirement isn't met, (because it requires separate installation of the module). :)
> 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
[jira] [Reopened] (CASSANDRA-3188) cqlsh 2.0
Posted by "paul cannon (Reopened) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
paul cannon reopened CASSANDRA-3188:
------------------------------------
Looks like, also, bin/cqlsh doesn't have svn:executable set.
> 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.3
>
> Attachments: 3188.patch5.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
[jira] [Resolved] (CASSANDRA-3188) cqlsh 2.0
Posted by "Jonathan Ellis (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-3188.
---------------------------------------
Resolution: Fixed
done
> 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.3
>
> Attachments: 3188.patch5.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
[jira] [Commented] (CASSANDRA-3188) cqlsh 2.0
Posted by "Jonathan Ellis (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13139868#comment-13139868 ]
Jonathan Ellis commented on CASSANDRA-3188:
-------------------------------------------
Right. I see cqlsh (this new version) as strictly superior to the old cli and I want it to become the default thing people reach for.
So noted that You Told Me So. :)
> 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
[jira] [Updated] (CASSANDRA-3188) cqlsh 2.0
Posted by "paul cannon (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
paul cannon updated CASSANDRA-3188:
-----------------------------------
Attachment: (was: 3188.patch1.txt)
> 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
[jira] [Commented] (CASSANDRA-3188) cqlsh 2.0
Posted by "Jonathan Ellis (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13139527#comment-13139527 ]
Jonathan Ellis commented on CASSANDRA-3188:
-------------------------------------------
Why put it in the tree? Because it's a core part of the distribution, or will be. By analogy, it would feel wrong for psql to be a separate project from postgresql core.
> 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
[jira] [Commented] (CASSANDRA-3188) cqlsh 2.0
Posted by "Jonathan Ellis (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13124375#comment-13124375 ]
Jonathan Ellis commented on CASSANDRA-3188:
-------------------------------------------
I think we can assume readline is present on non-Windows platforms (that is the only exception the python stdlib docs makes).
> 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
[jira] [Commented] (CASSANDRA-3188) cqlsh 2.0
Posted by "paul cannon (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13125914#comment-13125914 ]
paul cannon commented on CASSANDRA-3188:
----------------------------------------
bq. Does it make sense to try to recover from thrift not being installed? I think I'd rather raise a fatal error explaining the problem and how to fix it. Or just leave it as a bare import and assume that if you're not installing from a package you can deal with it. (pypi does allow specifiying dependencies right?)
It doesn't help anything right now to try and recover- it's just a bit of future-proofing for when we no longer need Thrift. I just tried to make the Thrift parts easy to identify and excise when appropriate.
bq. I'm not a fan of adding another layer of default options besides the ones in the server and in the Thrift CfDef. I also think the use case here is misguided. (It's used to provide a "minimal" schema dump, skipping options that are unchanged from the default.) If we change the defaults next release, we want schemas being imported there to preserve their existing settings. So I think verbosity is a good thing in this case.
Fair enough- I've found that a bunch of defaults are different between existing c* versions already. It does bother me, though, that you get a big wall of text from the DESCRIBE commands, even when you only want to see the meatiest parts. Maybe that can be eased with some coloring, or maybe a different version of DESCRIBE- something like {{DESCRIBE whatever SHORT}} to leave off display of the options which are generally less interesting for everyday use?
bq. cql_type_to_apache_class feels like it might belong in the driver's cql.marshal. (Shame on you Python stdlib for still not including a BiMap. BiDict?)
I agree. I tried to keep driver changes to a minimum so I wouldn't have to depend on the very-newest cassandra-dbapi2 release, but perhaps that's not very useful.
I have a new version with some fixes, additions, and lots of nice help to upload later today.
> 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
[jira] [Updated] (CASSANDRA-3188) cqlsh 2.0
Posted by "paul cannon (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
paul cannon updated CASSANDRA-3188:
-----------------------------------
Attachment: 3188.patch2.txt
3188.patch2.txt: lots more docs, both in the cqlsh online help and a revamped CQL.textile.
> 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, 3188.patch2.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
[jira] [Updated] (CASSANDRA-3188) cqlsh 2.0
Posted by "paul cannon (Updated) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (CASSANDRA-3188) cqlsh 2.0
Posted by "paul cannon (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13124370#comment-13124370 ]
paul cannon commented on CASSANDRA-3188:
----------------------------------------
As I recall, we weren't going to make an effort to support windows here yet- just making sure we didn't paint ourselves into a corner for when we do.
But yeah, a missing readline should probably be caught and handled regardless.
> 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
[jira] [Updated] (CASSANDRA-3188) cqlsh 2.0
Posted by "paul cannon (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
paul cannon updated CASSANDRA-3188:
-----------------------------------
Attachment: (was: 3188.patch3.txt)
> 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
[jira] [Commented] (CASSANDRA-3188) cqlsh 2.0
Posted by "Eric Evans (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (CASSANDRA-3188) cqlsh 2.0
Posted by "Jonathan Ellis (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13125465#comment-13125465 ]
Jonathan Ellis commented on CASSANDRA-3188:
-------------------------------------------
Autocomplete is tasty. Thanks for including examples of the different token counts in the comments.
Does it make sense to try to recover from thrift not being installed? I think I'd rather raise a fatal error explaining the problem and how to fix it. Or just leave it as a bare import and assume that if you're not installing from a package you can deal with it. (pypi does allow specifiying dependencies right?)
I'm not a fan of adding another layer of default options besides the ones in the server and in the Thrift CfDef. I also think the use case here is misguided. (It's used to provide a "minimal" schema dump, skipping options that are unchanged from the default.) If we change the defaults next release, we want schemas being imported there to preserve their existing settings. So I think verbosity is a good thing in this case.
cql_type_to_apache_class feels like it might belong in the driver's cql.marshal. (Shame on you Python stdlib for still not including a BiMap. BiDict?)
(I do think that ASSUME belongs in cqlsh as you have it here and not as a part of the CQL language itself: programmatic clients are free to unpack bytestrings any way they please, the problem is how to solve this for human consumption in an interactive session.)
> 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
[jira] [Commented] (CASSANDRA-3188) cqlsh 2.0
Posted by "paul cannon (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (CASSANDRA-3188) cqlsh 2.0
Posted by "paul cannon (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13136246#comment-13136246 ]
paul cannon commented on CASSANDRA-3188:
----------------------------------------
Now needs a bit of change to support CASSANDRA-3130.
> 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.patch1.txt, 3188.patch2.txt, 3188.patch3.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
[jira] [Commented] (CASSANDRA-3188) cqlsh 2.0
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (CASSANDRA-3188) cqlsh 2.0
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13103956#comment-13103956 ]
Jonathan Ellis commented on CASSANDRA-3188:
-------------------------------------------
bq. cassandra-cli uses JMX for a few of its cluster-inspection duties
If this is important, we can look at making mx4j an official dependency instead of just supported-if-you-happen-to-have-it-around.
> 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
[jira] [Commented] (CASSANDRA-3188) cqlsh 2.0
Posted by "paul cannon (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13136267#comment-13136267 ]
paul cannon commented on CASSANDRA-3188:
----------------------------------------
It was encapsulated. But cqlsh needs to do elementary CQL parsing on the input in order to provide the ASSUME functionality, context-sensitive tab completion, and tracking of the current keyspace.
> 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.patch1.txt, 3188.patch2.txt, 3188.patch3.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
[jira] [Updated] (CASSANDRA-3188) cqlsh 2.0
Posted by "paul cannon (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
paul cannon updated CASSANDRA-3188:
-----------------------------------
Attachment: 3188.patch5.txt
patch5 rearranges things a bit for tarball inclusion, adds the Apache License headers to the remaining files, fixes a small tab-completion bug, adds a --version option to cqlsh, and moves cqlsh to bin/.
> 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.3
>
> Attachments: 3188.patch5.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
[jira] [Commented] (CASSANDRA-3188) cqlsh 2.0
Posted by "Jonathan Ellis (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13136252#comment-13136252 ]
Jonathan Ellis commented on CASSANDRA-3188:
-------------------------------------------
We tried to keep 3130 encapsulated in the server, what went wrong?
> 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.patch1.txt, 3188.patch2.txt, 3188.patch3.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