cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-8706) Make it possible to configure different compaction strategies for repaired and unrepaired data
Date Tue, 03 Feb 2015 21:12:34 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-8706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis updated CASSANDRA-8706:
--------------------------------------
    Fix Version/s:     (was: 3.0)

Let's do that -- leaving it open, but fixver empty for now.

> 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
>            Priority: Minor
>
> 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)

Mime
View raw message