You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Marcus Eriksson (JIRA)" <ji...@apache.org> on 2015/08/17 13:34:46 UTC

[jira] [Commented] (CASSANDRA-8671) Give compaction strategy more control over where sstables are created, including for flushing and streaming.

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

Marcus Eriksson commented on CASSANDRA-8671:
--------------------------------------------

could you rebase and push a branch so we get cassci results?

> Give compaction strategy more control over where sstables are created, including for flushing and streaming.
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-8671
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8671
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Blake Eggleston
>            Assignee: Blake Eggleston
>             Fix For: 3.x
>
>         Attachments: 0001-C8671-creating-sstable-writers-for-flush-and-stream-.patch, 8671-giving-compaction-strategies-more-control-over.txt
>
>
> This would enable routing different partitions to different disks based on some user defined parameters.
> My initial take on how to do this would be to make an interface from SSTableWriter, and have a table's compaction strategy do all SSTableWriter instantiation. Compaction strategies could then implement their own SSTableWriter implementations (which basically wrap one or more normal sstablewriters) for compaction, flushing, and streaming. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)