cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michaël Figuière (JIRA) <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4454) Add a notice on cqlsh startup about CQL2/3 switches
Date Fri, 20 Jul 2012 22:43:34 GMT

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

Michaël Figuière commented on CASSANDRA-4454:
---------------------------------------------

Indeed the way it's currently mentioned is enough for experienced users. On the other hand
newcomers might not even be familiar with the fact we're in the middle of a CQL grammar switch,
then they run cqlsh with default settings, copy paste an example of CQL3 DDL with a composite
column from a web page and end up with something like this:

{noformat}
cqlsh:mykeyspace> CREATE TABLE timeline (
              ...          user_id varchar,
              ...          tweet_id uuid,
              ...          author varchar,
              ...          body varchar,
              ...          PRIMARY KEY (user_id, tweet_id));
Bad Request: line 6:40 mismatched input ')' expecting EOF
{noformat}

This is an example of confusing error you can have pushing CQL3 commands. The fact that several
guys had difficulties with this situation tends to show that a message like "{{Consider using
-3 switch to enable CQL3}} would be useful, either at startup or when a CQL2/3 grammar mismatch
occur. As the former is trivial to implement, I was suggesting it. 
                
> 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

       

Mime
View raw message