You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Claudio Atzori (JIRA)" <ji...@apache.org> on 2012/05/22 16:53:40 UTC
[jira] [Created] (CASSANDRA-4272) Keyspace name case sensitivity
Claudio Atzori created CASSANDRA-4272:
-----------------------------------------
Summary: Keyspace name case sensitivity
Key: CASSANDRA-4272
URL: https://issues.apache.org/jira/browse/CASSANDRA-4272
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 1.1.0
Environment: cassandra-cli
Reporter: Claudio Atzori
I've been trying to define a keyspace from the cassandra-cli on a cluster of 5 nodes (1.1.0), but I got a NotFoundException(), after a schema agreement accross the cluster message, which I guess It can be quite confusing, because the keyspace wasn't created at all.
[default@unknown] create keyspace 'MY_NEW_KEYSPACE' with placement_strategy = 'org.apache.cassandra.locator.SimpleStrategy' and strategy_options = {replication_factor:2} ;
ba6a9a70-e983-3b9c-bd8c-b0022865bb3e
Waiting for schema agreement...
... schemas agree across the cluster
NotFoundException()
BTW, I've been able to create the keyspace by lowercasing its name.
--
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] [Resolved] (CASSANDRA-4272) Keyspace name case sensitivity
Posted by "Claudio Atzori (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claudio Atzori resolved CASSANDRA-4272.
---------------------------------------
Resolution: Invalid
> Keyspace name case sensitivity
> ------------------------------
>
> Key: CASSANDRA-4272
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4272
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.0
> Environment: cassandra-cli
> Reporter: Claudio Atzori
>
> I've been trying to define a keyspace from the cassandra-cli on a cluster of 5 nodes (1.1.0), but I got a NotFoundException(), after a schema agreement accross the cluster message, which I guess It can be quite confusing, because the keyspace wasn't created at all.
> [default@unknown] create keyspace 'MY_NEW_KEYSPACE' with placement_strategy = 'org.apache.cassandra.locator.SimpleStrategy' and strategy_options = {replication_factor:2} ;
> ba6a9a70-e983-3b9c-bd8c-b0022865bb3e
> Waiting for schema agreement...
> ... schemas agree across the cluster
> NotFoundException()
> BTW, I've been able to create the keyspace by lowercasing its name.
--
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] [Comment Edited] (CASSANDRA-4272) Keyspace name case
sensitivity
Posted by "Jure Koren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416954#comment-13416954 ]
Jure Koren edited comment on CASSANDRA-4272 at 7/18/12 9:15 AM:
----------------------------------------------------------------
I don't think recreating a cluster is a good enough solution for this. I have the same problem and can't recreate an empty cluster.
Is there a way to prune deleted keys from the system keyspace? I can still list deleted keyspaces from the schema_keyspaces CF in the system keyspace, perhaps that's what causes problems.
I could create a keyspace with the same name, but different case before, but this doesn't work anymore:
[default@unknown] create keyspace test_Campaigns with placement_strategy = 'NetworkTopologyStrategy' and strategy_options = {DC_KOT : 1, DC_DELO : 1, DC_OFC : 1} and durable_writes = true;
62979db5-8643-31ad-b13a-289e66d8f414
Waiting for schema agreement...
... schemas agree across the cluster
NotFoundException()
[default@unknown] create keyspace test_campaigns with placement_strategy = 'NetworkTopologyStrategy' and strategy_options = {DC_KOT : 1, DC_DELO : 1, DC_OFC : 1} and durable_writes = true;
62979db5-8643-31ad-b13a-289e66d8f414
Waiting for schema agreement...
... schemas agree across the cluster
NotFoundException()
was (Author: jurek):
I don't think recreating a cluster is a good enough solution for this. I have the same problem and can't recreate an empty cluster.
Is there a way to prune deleted keys from the system keyspace? I can still list deleted keyspaces from the schema_keyspaces CF in the system keyspace, perhaps that's what causes problems.
> Keyspace name case sensitivity
> ------------------------------
>
> Key: CASSANDRA-4272
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4272
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.0
> Environment: cassandra-cli
> Reporter: Claudio Atzori
>
> I've been trying to define a keyspace from the cassandra-cli on a cluster of 5 nodes (1.1.0), but I got a NotFoundException(), after a schema agreement accross the cluster message, which I guess It can be quite confusing, because the keyspace wasn't created at all.
> [default@unknown] create keyspace 'MY_NEW_KEYSPACE' with placement_strategy = 'org.apache.cassandra.locator.SimpleStrategy' and strategy_options = {replication_factor:2} ;
> ba6a9a70-e983-3b9c-bd8c-b0022865bb3e
> Waiting for schema agreement...
> ... schemas agree across the cluster
> NotFoundException()
> BTW, I've been able to create the keyspace by lowercasing its name.
--
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-4272) Keyspace name case sensitivity
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281017#comment-13281017 ]
Jonathan Ellis commented on CASSANDRA-4272:
-------------------------------------------
Can you reproduce this with an empty cluster? I wonder if an incomplete creation was conflicting here.
> Keyspace name case sensitivity
> ------------------------------
>
> Key: CASSANDRA-4272
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4272
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.0
> Environment: cassandra-cli
> Reporter: Claudio Atzori
>
> I've been trying to define a keyspace from the cassandra-cli on a cluster of 5 nodes (1.1.0), but I got a NotFoundException(), after a schema agreement accross the cluster message, which I guess It can be quite confusing, because the keyspace wasn't created at all.
> [default@unknown] create keyspace 'MY_NEW_KEYSPACE' with placement_strategy = 'org.apache.cassandra.locator.SimpleStrategy' and strategy_options = {replication_factor:2} ;
> ba6a9a70-e983-3b9c-bd8c-b0022865bb3e
> Waiting for schema agreement...
> ... schemas agree across the cluster
> NotFoundException()
> BTW, I've been able to create the keyspace by lowercasing its name.
--
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-4272) Keyspace name case sensitivity
Posted by "Claudio Atzori (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13282491#comment-13282491 ]
Claudio Atzori commented on CASSANDRA-4272:
-------------------------------------------
Ok, nevermind. I really needed to start over with an empty cluster. We've been using those 5 nodes for development since cassandra 0.8 and I guess it held quite old test data, so a fresh start was needed indeed.
> Keyspace name case sensitivity
> ------------------------------
>
> Key: CASSANDRA-4272
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4272
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.0
> Environment: cassandra-cli
> Reporter: Claudio Atzori
>
> I've been trying to define a keyspace from the cassandra-cli on a cluster of 5 nodes (1.1.0), but I got a NotFoundException(), after a schema agreement accross the cluster message, which I guess It can be quite confusing, because the keyspace wasn't created at all.
> [default@unknown] create keyspace 'MY_NEW_KEYSPACE' with placement_strategy = 'org.apache.cassandra.locator.SimpleStrategy' and strategy_options = {replication_factor:2} ;
> ba6a9a70-e983-3b9c-bd8c-b0022865bb3e
> Waiting for schema agreement...
> ... schemas agree across the cluster
> NotFoundException()
> BTW, I've been able to create the keyspace by lowercasing its name.
--
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-4272) Keyspace name case sensitivity
Posted by "Jure Koren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416954#comment-13416954 ]
Jure Koren commented on CASSANDRA-4272:
---------------------------------------
I don't think recreating a cluster is a good enough solution for this. I have the same problem and can't recreate an empty cluster.
Is there a way to prune deleted keys from the system keyspace? I can still list deleted keyspaces from the schema_keyspaces CF in the system keyspace, perhaps that's what causes problems.
> Keyspace name case sensitivity
> ------------------------------
>
> Key: CASSANDRA-4272
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4272
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.0
> Environment: cassandra-cli
> Reporter: Claudio Atzori
>
> I've been trying to define a keyspace from the cassandra-cli on a cluster of 5 nodes (1.1.0), but I got a NotFoundException(), after a schema agreement accross the cluster message, which I guess It can be quite confusing, because the keyspace wasn't created at all.
> [default@unknown] create keyspace 'MY_NEW_KEYSPACE' with placement_strategy = 'org.apache.cassandra.locator.SimpleStrategy' and strategy_options = {replication_factor:2} ;
> ba6a9a70-e983-3b9c-bd8c-b0022865bb3e
> Waiting for schema agreement...
> ... schemas agree across the cluster
> NotFoundException()
> BTW, I've been able to create the keyspace by lowercasing its name.
--
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