[ 
https://issues.apache.org/jira/browse/CASSANDRA-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13170385#comment-13170385
 ] 

Sylvain Lebresne commented on CASSANDRA-2749:
---------------------------------------------

{quote}
On the other hand, we allow arbitrary-length KS + CF names (up to 64K iirc) so 
UUID aside we're already in trouble on ext3/ext4, xfs, and ntfs, which all 
support max filename length of ~256. I'm starting to think we should move these 
into the metadata component instead of the filename.
{quote}

The thing with the metadata component is that from a code perspective, there is 
lots of places where we want to create a Descriptor, which involves extracting 
the keyspace/cf names only based on the filename. Adding the necessity to 
locate and read the metadata in those places will likely don't be very fun.

So I'd be in favor of just limiting the keyspace and column family names. It's 
one for which there is no real point to have very long names. Limiting each one 
to 32 characters shouldn't be a strong limitation.
                
> fine-grained control over data directories
> ------------------------------------------
>
>                 Key: CASSANDRA-2749
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2749
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Jonathan Ellis
>            Priority: Minor
>             Fix For: 1.1
>
>         Attachments: 
> 0001-Make-it-possible-to-put-column-families-in-subdirect.patch, 
> 0001-add-new-directory-layout.patch, 
> 0001-non-backwards-compatible-patch-for-2749-putting-cfs-.patch.gz, 
> 0002-fix-unit-tests.patch, 2749.tar.gz, 2749_backwards_compatible_v1.patch, 
> 2749_backwards_compatible_v2.patch, 2749_backwards_compatible_v3.patch, 
> 2749_backwards_compatible_v4.patch, 
> 2749_backwards_compatible_v4_rebase1.patch, 2749_not_backwards.tar.gz, 
> 2749_proper.tar.gz
>
>
> Currently Cassandra supports multiple data directories but no way to control 
> what sstables are placed where. Particularly for systems with mixed SSDs and 
> rotational disks, it would be nice to pin frequently accessed columnfamilies 
> to the SSDs.
> Postgresql does this with tablespaces 
> (http://www.postgresql.org/docs/9.0/static/manage-ag-tablespaces.html) but we 
> should probably avoid using that name because of confusing similarity to 
> "keyspaces."

--
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

        

Reply via email to