Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 30 Jan 2015 13:18:34 +0000 (UTC)
From: "Marcus Eriksson (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12771333.1422623876000.214964.1422623914794@Atlassian.JIRA>
In-Reply-To: <JIRA.12771333.1422623876000@Atlassian.JIRA>
References: <JIRA.12771333.1422623876000@Atlassian.JIRA>
 <JIRA.12771333.1422623876298@arcas>
Subject: [jira] [Created] (CASSANDRA-8706) Make it possible to configure
 different compaction strategies for repaired and unrepaired data
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Marcus Eriksson created CASSANDRA-8706:
------------------------------------------

             Summary: Make it possible to configure different compaction strategies for repaired and unrepaired data
                 Key: CASSANDRA-8706
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8706
             Project: Cassandra
          Issue Type: Improvement
            Reporter: Marcus Eriksson
             Fix For: 3.0


In CASSANDRA-8004 we introduced WrappingCompactionStrategy which handles repaired and unrepaired sstables for compaction - it acts as there is still a single compaction strategy, but underneath it runs 2 different instances of the configured strategy. Main purpose of this was to remove any duplicated repaired/unrepaired logic from the actual compaction strategies and collect them in one place.

We should make it possible for users to configure different strategies for the different sets of data - if a user wants to run STCS on unrepaired data and LCS on repaired, it should be possible.

This ticket includes replacing WrappingCompactionStrategy with something that does not extend AbstractCompactionStrategy as that part is quite confusing.


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