You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Eric Evans (JIRA)" <ji...@apache.org> on 2010/06/12 17:29:13 UTC
[jira] Created: (CASSANDRA-1185) determine legal keyspace/column
family names and validate
determine legal keyspace/column family names and validate
---------------------------------------------------------
Key: CASSANDRA-1185
URL: https://issues.apache.org/jira/browse/CASSANDRA-1185
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 0.7
Reporter: Eric Evans
Priority: Minor
Since keyspace and column family names are used to derive the directory and filenames where data is stored, so some thought should be given to which characters are legally allowed. Then, node-side validation should prevent the creation of namespaces that contain these characters, and produce a meaningful error message in the process.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-1185) determine legal keyspace/column
family names and validate
Posted by "Jeremy Hanna (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878281#action_12878281 ]
Jeremy Hanna commented on CASSANDRA-1185:
-----------------------------------------
Is there a way we could divorce names in Cassandra from names on the filesystem? It just seems like an odd implementation specific thing.
Maybe marking up special characters in a standard way?
I'm not sure why they are ties together in the first place though.
No matter what though validation and error messages are needed- I was just curious.
> determine legal keyspace/column family names and validate
> ---------------------------------------------------------
>
> Key: CASSANDRA-1185
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1185
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7
> Reporter: Eric Evans
> Priority: Minor
>
> Since keyspace and column family names are used to derive the directory and filenames where data is stored, so some thought should be given to which characters are legally allowed. Then, node-side validation should prevent the creation of namespaces that contain these characters, and produce a meaningful error message in the process.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-1185) determine legal keyspace/column
family names and validate
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878288#action_12878288 ]
Eric Evans commented on CASSANDRA-1185:
---------------------------------------
bq.
Is there a way we could divorce names in Cassandra from names on the filesystem? It just seems like an odd implementation specific thing.
You could, but I think this is a case where the cure would be worse than the disease. It's rather nice to be able to map keyspace and column family names to their respective locations in the filesystem, and I suspect that a lot of people have come to rely on this.
> determine legal keyspace/column family names and validate
> ---------------------------------------------------------
>
> Key: CASSANDRA-1185
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1185
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7
> Reporter: Eric Evans
> Priority: Minor
>
> Since keyspace and column family names are used to derive the directory and filenames where data is stored, so some thought should be given to which characters are legally allowed. Then, node-side validation should prevent the creation of namespaces that contain these characters, and produce a meaningful error message in the process.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (CASSANDRA-1185) determine legal
keyspace/column family names and validate
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878288#action_12878288 ]
Eric Evans edited comment on CASSANDRA-1185 at 6/12/10 1:26 PM:
----------------------------------------------------------------
bq. Is there a way we could divorce names in Cassandra from names on the filesystem? It just seems like an odd implementation specific thing.
You could, but I think this is a case where the cure would be worse than the disease. It's rather nice to be able to map keyspace and column family names to their respective locations in the filesystem, and I suspect that a lot of people have come to rely on this.
was (Author: urandom):
bq.
Is there a way we could divorce names in Cassandra from names on the filesystem? It just seems like an odd implementation specific thing.
You could, but I think this is a case where the cure would be worse than the disease. It's rather nice to be able to map keyspace and column family names to their respective locations in the filesystem, and I suspect that a lot of people have come to rely on this.
> determine legal keyspace/column family names and validate
> ---------------------------------------------------------
>
> Key: CASSANDRA-1185
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1185
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7
> Reporter: Eric Evans
> Priority: Minor
>
> Since keyspace and column family names are used to derive the directory and filenames where data is stored, so some thought should be given to which characters are legally allowed. Then, node-side validation should prevent the creation of namespaces that contain these characters, and produce a meaningful error message in the process.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.