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 2014/11/05 10:28:34 UTC
[jira] [Created] (CASSANDRA-8255) Improve the way we handle
compaction strategies
Marcus Eriksson created CASSANDRA-8255:
------------------------------------------
Summary: Improve the way we handle compaction strategies
Key: CASSANDRA-8255
URL: https://issues.apache.org/jira/browse/CASSANDRA-8255
Project: Cassandra
Issue Type: Bug
Reporter: Marcus Eriksson
Fix For: 3.0
After CASSANDRA-8004 it could be a bit confusing since we have a compaction strategy that is 'special' (WrappingCompactionStrategy). This ticket aims to refactor that.
Goals;
* make it possible to configure compaction strategies for repaired/unrepaired separately (someone might want to run STCS for unrepaired and LCS for repaired or with LCS with 5MB sstables for unrepaired and 160MB for repaired etc)
* replace WrappingCompactionStrategy with something more fitting (only reason it was introduced in #8004 was to make the change as transparent as possible)
* pave the way for CASSANDRA-5449 and CASSANDRA-6696 (6696 currently runs one compaction strategy per vnode, having this better in place could simplify)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)