You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Stu Hood (JIRA)" <ji...@apache.org> on 2011/01/15 09:38:45 UTC

[jira] Created: (CASSANDRA-1990) Store GC info once per SSTable

Store GC info once per SSTable
------------------------------

                 Key: CASSANDRA-1990
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1990
             Project: Cassandra
          Issue Type: Improvement
          Components: Core
            Reporter: Stu Hood
             Fix For: 0.8


Deleted columns are currently marked with the server time when they were deleted, but since it is not possible to perform GC at a resolution lower than an entire SSTable, it would probably make sense to remove the "markedForDeleteAt" field and use the SSTable flush time to indicate it.

It would make the most sense to tackle this during or soon after CASSANDRA-674.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (CASSANDRA-1990) Store GC info once per SSTable

Posted by "Stu Hood (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stu Hood resolved CASSANDRA-1990.
---------------------------------

    Resolution: Invalid

Uh, sorry: this makes no sense.

> Store GC info once per SSTable
> ------------------------------
>
>                 Key: CASSANDRA-1990
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1990
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Stu Hood
>             Fix For: 0.8
>
>
> Deleted columns are currently marked with the server time when they were deleted, but since it is not possible to perform GC at a resolution lower than an entire SSTable, it would probably make sense to remove the "markedForDeleteAt" field and use the SSTable flush time to indicate it.
> It would make the most sense to tackle this during or soon after CASSANDRA-674.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.