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

Jonathan Ellis commented on CASSANDRA-2749:
-------------------------------------------

Did some more research on path limitations:

NTFS is technically okay with paths up to 32K long[1], but the windows api is 
limited to 256[2].  Common Linux filesystems have a limit of 255 bytes per path 
*component* (i.e. directory or filename) but no total path limit.  However, 
Linux defines PATH_MAX and FILENAME_MAX, both 4096. [3]

[1] http://en.wikipedia.org/wiki/Comparison_of_file_systems
[2] http://msdn.microsoft.com/en-us/library/aa365247.aspx
[3] http://serverfault.com/questions/9546/filename-length-limits-on-linux

In short: restricting KS and CF names to 32 characters is a good idea for the 
benefit of Windows portability.  However, we may want to exempt Linux systems 
from the startup length check to allow easier upgrades.
                
> 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
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>             Fix For: 1.1.0
>
>         Attachments: 0001-2749.patch, 
> 0001-Make-it-possible-to-put-column-families-in-subdirect.patch, 
> 0001-non-backwards-compatible-patch-for-2749-putting-cfs-.patch.gz, 
> 0002-fix-unit-tests.patch, 0003-Fixes.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