You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "paul cannon (Created) (JIRA)" <ji...@apache.org> on 2011/10/12 00:11:12 UTC
[jira] [Created] (CASSANDRA-3350) Can't USE numeric keyspace names
in CQL
Can't USE numeric keyspace names in CQL
---------------------------------------
Key: CASSANDRA-3350
URL: https://issues.apache.org/jira/browse/CASSANDRA-3350
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 0.8.0 beta 2
Reporter: paul cannon
Priority: Minor
Cassandra allows keyspace names to start with a digit or an underscore (see o.a.c.db.migration.Migration.isLegalName), but CQL's {{USE}} statement only accepts a CQL identifier, which must start with a letter. So there's no way to use a keyspace named "142" or "_hi_" in CQL, for example.
The {{USE}} statement should accept string literals and integers as well as identifiers, and CQL identifiers ({{IDENT}}) should probably allow starting with the underscore.
--
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-3350) Can't USE numeric keyspace
names in CQL
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13125922#comment-13125922 ]
Hudson commented on CASSANDRA-3350:
-----------------------------------
Integrated in Cassandra-0.8 #367 (See [https://builds.apache.org/job/Cassandra-0.8/367/])
allow numeric keyspace names in USE statement
patch by pyaskevich; reviewed by jbellis for CASSANDRA-3350
jbellis : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1182413
Files :
* /cassandra/branches/cassandra-0.8/CHANGES.txt
* /cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/cql/Cql.g
* /cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/cql/QueryProcessor.java
> Can't USE numeric keyspace names in CQL
> ---------------------------------------
>
> Key: CASSANDRA-3350
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3350
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.8.0 beta 2
> Reporter: paul cannon
> Assignee: Pavel Yaskevich
> Priority: Minor
> Labels: lhf
> Fix For: 0.8.8, 1.0.1
>
> Attachments: CASSANDRA-3350.patch
>
>
> Cassandra allows keyspace names to start with a digit or an underscore (see o.a.c.db.migration.Migration.isLegalName), but CQL's {{USE}} statement only accepts a CQL identifier, which must start with a letter. So there's no way to use a keyspace named "142" or "\_hi\_" in CQL, for example.
> The {{USE}} statement should accept string literals and integers as well as identifiers, and CQL identifiers ({{IDENT}}) should probably allow starting with the underscore.
--
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-3350) Can't USE numeric keyspace names
in CQL
Posted by "Pavel Yaskevich (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Yaskevich updated CASSANDRA-3350:
---------------------------------------
Attachment: CASSANDRA-3350.patch
> Can't USE numeric keyspace names in CQL
> ---------------------------------------
>
> Key: CASSANDRA-3350
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3350
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.8.0 beta 2
> Reporter: paul cannon
> Assignee: Pavel Yaskevich
> Priority: Minor
> Labels: lhf
> Fix For: 0.8.8, 1.0.1
>
> Attachments: CASSANDRA-3350.patch
>
>
> Cassandra allows keyspace names to start with a digit or an underscore (see o.a.c.db.migration.Migration.isLegalName), but CQL's {{USE}} statement only accepts a CQL identifier, which must start with a letter. So there's no way to use a keyspace named "142" or "\_hi\_" in CQL, for example.
> The {{USE}} statement should accept string literals and integers as well as identifiers, and CQL identifiers ({{IDENT}}) should probably allow starting with the underscore.
--
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-3350) Can't USE numeric keyspace names
in CQL
Posted by "Jonathan Ellis (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-3350:
--------------------------------------
Fix Version/s: 1.0.1
0.8.8
Assignee: Pavel Yaskevich
> Can't USE numeric keyspace names in CQL
> ---------------------------------------
>
> Key: CASSANDRA-3350
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3350
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.8.0 beta 2
> Reporter: paul cannon
> Assignee: Pavel Yaskevich
> Priority: Minor
> Labels: lhf
> Fix For: 0.8.8, 1.0.1
>
>
> Cassandra allows keyspace names to start with a digit or an underscore (see o.a.c.db.migration.Migration.isLegalName), but CQL's {{USE}} statement only accepts a CQL identifier, which must start with a letter. So there's no way to use a keyspace named "142" or "\_hi\_" in CQL, for example.
> The {{USE}} statement should accept string literals and integers as well as identifiers, and CQL identifiers ({{IDENT}}) should probably allow starting with the underscore.
--
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-3350) Can't USE numeric keyspace names
in CQL
Posted by "paul cannon (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
paul cannon updated CASSANDRA-3350:
-----------------------------------
Description:
Cassandra allows keyspace names to start with a digit or an underscore (see o.a.c.db.migration.Migration.isLegalName), but CQL's {{USE}} statement only accepts a CQL identifier, which must start with a letter. So there's no way to use a keyspace named "142" or "\_hi\_" in CQL, for example.
The {{USE}} statement should accept string literals and integers as well as identifiers, and CQL identifiers ({{IDENT}}) should probably allow starting with the underscore.
was:
Cassandra allows keyspace names to start with a digit or an underscore (see o.a.c.db.migration.Migration.isLegalName), but CQL's {{USE}} statement only accepts a CQL identifier, which must start with a letter. So there's no way to use a keyspace named "142" or "_hi_" in CQL, for example.
The {{USE}} statement should accept string literals and integers as well as identifiers, and CQL identifiers ({{IDENT}}) should probably allow starting with the underscore.
> Can't USE numeric keyspace names in CQL
> ---------------------------------------
>
> Key: CASSANDRA-3350
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3350
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.8.0 beta 2
> Reporter: paul cannon
> Priority: Minor
> Labels: lhf
>
> Cassandra allows keyspace names to start with a digit or an underscore (see o.a.c.db.migration.Migration.isLegalName), but CQL's {{USE}} statement only accepts a CQL identifier, which must start with a letter. So there's no way to use a keyspace named "142" or "\_hi\_" in CQL, for example.
> The {{USE}} statement should accept string literals and integers as well as identifiers, and CQL identifiers ({{IDENT}}) should probably allow starting with the underscore.
--
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-3350) Can't USE numeric keyspace
names in CQL
Posted by "Jonathan Ellis (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13125810#comment-13125810 ]
Jonathan Ellis commented on CASSANDRA-3350:
-------------------------------------------
+1
> Can't USE numeric keyspace names in CQL
> ---------------------------------------
>
> Key: CASSANDRA-3350
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3350
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.8.0 beta 2
> Reporter: paul cannon
> Assignee: Pavel Yaskevich
> Priority: Minor
> Labels: lhf
> Fix For: 0.8.8, 1.0.1
>
> Attachments: CASSANDRA-3350.patch
>
>
> Cassandra allows keyspace names to start with a digit or an underscore (see o.a.c.db.migration.Migration.isLegalName), but CQL's {{USE}} statement only accepts a CQL identifier, which must start with a letter. So there's no way to use a keyspace named "142" or "\_hi\_" in CQL, for example.
> The {{USE}} statement should accept string literals and integers as well as identifiers, and CQL identifiers ({{IDENT}}) should probably allow starting with the underscore.
--
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