[ https://issues.apache.org/jira/browse/CASSANDRA-10540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588733#comment-16588733 ]
Kurt Greaves commented on CASSANDRA-10540: ------------------------------------------ [~krummas] Any hope of getting this in by 4.0? I'd be committed to testing/verifying/benchmarking post freeze if we can get it in. Code-wise seems fine to me, and our testing so far seems to show that it's viable. Any reason we can't get this committed and fix/revert during freeze if issues come up? > 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 > Priority: Major > Labels: 4.0-feature-freeze-review-requested, compaction, lcs, > vnodes > Fix For: 4.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 (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org