cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-9780) Get rid of CFMetaData isPurged(), markPurged()
Date Sun, 12 Jul 2015 10:38:04 GMT
Aleksey Yeschenko created CASSANDRA-9780:
--------------------------------------------

             Summary: Get rid of CFMetaData isPurged(), markPurged()
                 Key: CASSANDRA-9780
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9780
             Project: Cassandra
          Issue Type: Bug
            Reporter: Aleksey Yeschenko
            Assignee: Aleksey Yeschenko
            Priority: Minor


CASSANDRA-3578 added a new {{isPurged}} field to {{CFMetaData}}. It's only being used by {{CommitLogSegment.markDirty()}}.

The linked patch removed the field and all the purge-related methods, replacing that condition
with {{!Schema.instance.hasCF()}}.

That said, I'm not sure that the check makes sense at all, with CASSANDRA-5202.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message