[
https://issues.apache.org/jira/browse/CASSANDRA-9780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14624432#comment-14624432
]
Benedict commented on CASSANDRA-9780:
-------------------------------------
I'd prefer we not do concurrent map lookups unnecessarily on critical paths,
though it is certainly not a tremendous burden compared to other activities we
currently must undertake.
Fortunately I think you're right: this is no longer necessary, as we will not
replay for unknown CFs. So let's just remove it entirely.
> 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)
