cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jure Koren (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4272) Keyspace name case sensitivity
Date Wed, 18 Jul 2012 09:14:34 GMT


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:
>             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:!default.jspa
For more information on JIRA, see:


View raw message