You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Alex P (JIRA)" <ji...@apache.org> on 2014/04/26 11:55:16 UTC
[jira] [Commented] (CASSANDRA-7094) Keyspace name quoting is
handled inconsistently and strangely
[ https://issues.apache.org/jira/browse/CASSANDRA-7094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13981934#comment-13981934 ]
Alex P commented on CASSANDRA-7094:
-----------------------------------
CQL is case-insensitive, so the behavior of USE, etc is correct. DESCRIBE is not part of CQL though, but it should probably preserve the case-insensitive behavior (to avoid confusions).
> Keyspace name quoting is handled inconsistently and strangely
> --------------------------------------------------------------
>
> Key: CASSANDRA-7094
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7094
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Environment: cassandra 1.2.16
> Reporter: Karl Mueller
> Assignee: Mikhail Stepura
> Priority: Trivial
>
> Keyspaces which are named starting with capital letters (and perhaps other things) sometimes require double quotes and sometimes do not.
> For example, describe works without quotes:
> cqlsh> describe keyspace ProductGenomeLocal;
> CREATE KEYSPACE "ProductGenomeLocal" WITH replication = {
> 'class': 'SimpleStrategy',
> 'replication_factor': '3'
> };
> USE "ProductGenomeLocal";
> [...]
> But use will not:
> cqlsh> use ProductGenomeLocal;
> Bad Request: Keyspace 'productgenomelocal' does not exist
> It seems that qoutes should only really be necessary when there's spaces or other symbols that need to be quoted.
> At the least, the acceptance or failures of quotes should be consistent.
> Other minor annoyance: tab expansion works in use and describe with quotes, but will not work in either without quotes.
--
This message was sent by Atlassian JIRA
(v6.2#6252)