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

Pavel Yaskevich commented on CASSANDRA-2749:
--------------------------------------------

Tested v4 on trunk and I see few test failures - LegacySSTableTest and 
ColumnFamilyStoreTest, it is related to how you determine what placement style 
is used for a given SSTable, feels like 
!DatabaseDescriptor.useSeparateCFDirectories() condition is insufficient. Also 
I think it would be correct to rename "one_directory_per_column_family" option 
to "use_separate_column_family_directories" with comment like "Useful when you 
have disks with different speeds (HDD/SSD) and you want explicitly distribute 
Column Families between them".
                
> 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, 
> 2749_backwards_compatible_v4_rebase1.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

        

Reply via email to