You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2012/07/20 20:49:35 UTC
[jira] [Commented] (CASSANDRA-4454) Add a notice on cqlsh startup
about CQL2/3 switches
[ https://issues.apache.org/jira/browse/CASSANDRA-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13419432#comment-13419432 ]
Brandon Williams commented on CASSANDRA-4454:
---------------------------------------------
It does actually tell you this on startup:
{noformat}
cassandra-3:/srv/cassandra# bin/cqlsh cassandra-3
Connected to Test Cluster at cassandra-3:9160.
[cqlsh 2.2.0 | Cassandra unknown | CQL spec 2.0.0 | Thrift protocol 19.33.0]
Use HELP for help.
cqlsh>
cassandra-3:/srv/cassandra# bin/cqlsh cassandra-3 -3
Connected to Test Cluster at cassandra-3:9160.
[cqlsh 2.2.0 | Cassandra unknown | CQL spec 3.0.0 | Thrift protocol 19.33.0]
Use HELP for help.
cqlsh>
{noformat}
> Add a notice on cqlsh startup about CQL2/3 switches
> ---------------------------------------------------
>
> Key: CASSANDRA-4454
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4454
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Affects Versions: 1.1.0
> Reporter: Michaël Figuière
> Assignee: paul cannon
> Priority: Minor
> Labels: cqlsh
> Fix For: 1.1.3
>
>
> Several developers I've talked with seem not to have noticed the {{-3}} switch immediately to run in CQL3 mode. If missing, cqlsh can obviously appear buggy in its way to handle CQL3.
> I guess it would be worth to add a notice at startup about this important detail.
--
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