[
https://issues.apache.org/jira/browse/CASSANDRA-3066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-3066:
--------------------------------------
Attachment: 3066-v2.txt
The real problem is allowing the create in the first place. v2 attached.
>From the comments:
{code}
// keyspace names must be unique case-insensitively because the
keyspace name beomes the directory
// where we store CF sstables. Names that differ only in case would
thus cause problems on
// case-insensitive filesystems (NTFS, most installations of HFS+).
{code}
(Also renamed the ListAccess methods to SchemaAccess.)
> Creating a keyspace SYSTEM cause issue
> --------------------------------------
>
> Key: CASSANDRA-3066
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3066
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.8.4
> Environment: Windows
> Reporter: Sébastien Giroux
> Priority: Minor
> Fix For: 0.8.5
>
> Attachments: 3066-v2.txt, CASSANDRA-3066-0.8-v1.patch
>
>
> It's possible to create a keyspace SYSTEM but impossible to do anything with
> it after.
> I know naming a keyspace SYSTEM is probably not a good idea but I was testing
> something on a test cluster and found this bug. Step to reproduce:
> connect localhost/9160;
> create keyspace SYSTEM;
> use SYSTEM;
> create column family test
> with comparator = UTF8Type and subcomparator = UTF8Type
> and default_validation_class = UTF8Type
> and column_metadata = [{column_name: title, validation_class: UTF8Type},
> {column_name: publisher, validation_class: UTF8Type}];
> And you get:
> system keyspace is not user-modifiable
> Although SYSTEM keyspace have been created and is a different keyspace as
> system.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
