cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Manoj Kanta Mainali (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4129) Cannot create keyspace with specific keywords through cli
Date Fri, 06 Apr 2012 14:27:23 GMT

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

Manoj Kanta Mainali commented on CASSANDRA-4129:
------------------------------------------------

For keyspace creation quotation, both single and double, does not work.

Here is a sample of error I get when creating keyspace

[default@unknown]create keyspace 'column';
Invalid keyspace name: 'column'

[default@unknown]create keyspace "column";
Syntax error at position 16: unexpected """ for `create keyspace "column";`.

Using quotation works for cf, but not for ks. Anything specific I need to do?
                
> Cannot create keyspace with specific keywords through cli
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-4129
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4129
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.0.8
>            Reporter: Manoj Kanta Mainali
>            Priority: Minor
>
> Keyspaces cannot be create when the keyspace name which are used as keywords in the cli,
such as 'keyspace', 'family' etc., through CLI. Even when surrounding the keyspace with quotation
does not solve the problem. However, such keyspaces can be created through other client such
as Hector.
> This is similar to the issue CASSANDRA-3195, in which the column families could not be
created. Similar to the solution of CASSANDRA-3195, using String keyspaceName = CliUtil.unescapeSQLString(statement.getChild(0).getText())
in executeAddKeySpace would solve the problem. 

--
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