You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2011/06/20 12:05:47 UTC
[jira] [Resolved] (CASSANDRA-2795) Autodelete empty rows
[ https://issues.apache.org/jira/browse/CASSANDRA-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sylvain Lebresne resolved CASSANDRA-2795.
-----------------------------------------
Resolution: Not A Problem
What you are seeing is range ghosts: http://wiki.apache.org/cassandra/FAQ#range_ghosts
The row *is* correctly deleted when all columns expires. It won't show as a range ghost once gc_grace seconds have passed.
> Autodelete empty rows
> ---------------------
>
> Key: CASSANDRA-2795
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2795
> Project: Cassandra
> Issue Type: Improvement
> Components: Core, Tools
> Affects Versions: 0.8.0
> Reporter: Pau Rodriguez
>
> In a system where every column expire using TTL. The rows persist, and they are empty.
> If is possible to also delete them if empty when last column had expired.
> I understand that this may be difficult to synchronize between all the cluster.
> If this behavior isn't good for all cases, maybe can be configured in a variable per Column Family.
> Alternatively could be a tool to removed empty rows along all the cluster, the problem to do that using the API is the time between the check is done and the remove is send.
> I think that is preferable to be done when last column has expired.
> Thanks in advance.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira