[
https://issues.apache.org/jira/browse/CASSANDRA-8671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14702962#comment-14702962
]
Marcus Eriksson commented on CASSANDRA-8671:
--------------------------------------------
Pushed a few updates to the branch here:
https://github.com/krummas/cassandra/commits/blake/8671-2 - biggest thing is
probably that I removed the CompactionAwareWriter interface and refactored the
API a bit.
Is this still enough for you?
tests here:
http://cassci.datastax.com/view/Dev/view/krummas/job/krummas-blake-8671-2-dtest/
http://cassci.datastax.com/view/Dev/view/krummas/job/krummas-blake-8671-2-testall/
> 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)
