[
https://issues.apache.org/jira/browse/CASSANDRA-10540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098155#comment-15098155
]
Marcus Eriksson commented on CASSANDRA-10540:
---------------------------------------------
pushed a [new branch|https://github.com/krummas/cassandra/commits/marcuse/10540]
dtest: http://cassci.datastax.com/job/krummas-marcuse-10540-dtest/
utest: http://cassci.datastax.com/job/krummas-marcuse-10540-testall/
I see that there are a few tests that seem to break, I'll look into those
> RangeAwareCompaction
> --------------------
>
> Key: CASSANDRA-10540
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10540
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Fix For: 3.x
>
>
> Broken out from CASSANDRA-6696, we should split sstables based on ranges
> during compaction.
> Requirements;
> * dont create tiny sstables - keep them bunched together until a single vnode
> is big enough (configurable how big that is)
> * make it possible to run existing compaction strategies on the per-range
> sstables
> We should probably add a global compaction strategy parameter that states
> whether this should be enabled or not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
