[jira] [Updated] (CASSANDRA-2749) fine-grained control over data directories

["Marcus Eriksson (Updated) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcus Eriksson updated CASSANDRA-2749:
---------------------------------------

    Attachment: 2749_backwards_compatible_v4.patch

v4 attached

* renamed DatabaseDescriptor method
* made file name checking case sensitive again...
* removed unused rename code (following the renameSSTables call path, it looks very strange, even in trunk, ill fix this after this patch is merged)
* cant figure out a way to make snapshotExists any better, im looking for a directory with the snapshot tag in all places, not sure if it could be wrong here (even if it is quite naive)
* removed dead todos


                
> 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: Marcus Eriksson
>            Priority: Minor
>             Fix For: 1.1
>
>         Attachments: 0001-Make-it-possible-to-put-column-families-in-subdirect.patch, 2749_backwards_compatible_v1.patch, 2749_backwards_compatible_v2.patch, 2749_backwards_compatible_v3.patch, 2749_backwards_compatible_v4.patch
>
>
> 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