cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3974) Per-CF TTL
Date Wed, 27 Jun 2012 07:35:46 GMT


Sylvain Lebresne commented on CASSANDRA-3974:

About the removeDeleted problem: I think that trying to force calls to removeDeleted (which
force an iteration of all columns) so that we can add the logic of this ticket is the wrong
approach (because it's inefficient for no good reason and doesn't make the code easier to
follow). I.e. currently the code to ignore irrelevant columns is split between QueryFilter.isRelevant()
and removeDeleted depending of which code path is taken (reads use isRelevant and compaction
uses removeDeleted basically). So I see mostly 2 options:
# we find a way to refactor the code so that we only ever ignore irrelevant columns in one
place. That would be great but again it's unclear how to do that correctly.
# we put the logic for this patch in both removeDeleted and isRelevant.

I'm personally fine going the second solution for the purpose of this ticket and keep the
first option in mind for later as a way to improve the code base. 
> Per-CF TTL
> ----------
>                 Key: CASSANDRA-3974
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>    Affects Versions: 1.2
>            Reporter: Jonathan Ellis
>            Assignee: Kirk True
>            Priority: Minor
>             Fix For: 1.2
>         Attachments: trunk-3974.txt, trunk-3974v2.txt, trunk-3974v3.txt
> Per-CF TTL would allow compaction optimizations ("drop an entire sstable's worth of expired
data") that we can't do with per-column.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message