[
https://issues.apache.org/jira/browse/CASSANDRA-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033258#comment-13033258
]
Alan Liang commented on CASSANDRA-1610:
---------------------------------------
"Looking quickly through that code, it looks a good chunk of the code is here
to support the expiring of sstables, and it's pretty much hardcoded. Isn't
there a way to encapsulate that better ?"
You're right, it might make more sense to allow a strategy to define how it
should expire the sstables.
I'll try and fix the description. But I want to keep the implemented strategies
with this ticket because they justify why the interfaces are worthwhile as Stu
pointed out above.
> Pluggable Compaction
> --------------------
>
> Key: CASSANDRA-1610
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1610
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Chris Goffinet
> Assignee: Alan Liang
> Priority: Minor
> Labels: compaction
> Fix For: 1.0
>
> Attachments: 0001-move-compaction-code-into-own-package.patch,
> 0002-Pluggable-Compaction-and-Expiration.patch
>
>
> In CASSANDRA-1608, I proposed some changes on how compaction works. I think
> it also makes sense to allow the ability to have pluggable compaction per CF.
> There could be many types of workloads where this makes sense. One example we
> had at Digg was to completely throw away certain SSTables after N days.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
