[ https://issues.apache.org/jira/browse/CASSANDRA-7784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14135082#comment-14135082 ]
Benedict commented on CASSANDRA-7784: ------------------------------------- Mostly LGTM, in fact it seems like an obvious improvement all round. But I'd either remove the \@Deprecated method entirely, or not deprecate it. Since it's only used in one very cheap to replace place, I'd simply drop it. > DROP table leaves the counter and row cache in a temporarily inconsistent > state that, if saved during, will cause an exception to be thrown > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: CASSANDRA-7784 > URL: https://issues.apache.org/jira/browse/CASSANDRA-7784 > Project: Cassandra > Issue Type: Bug > Reporter: Benedict > Assignee: Aleksey Yeschenko > Priority: Minor > Attachments: 7784.txt > > > It looks like this is quite a realistic race to hit reasonably often, since > we forceBlockingFlush after removing from Schema.cfIdMap, so there could be a > lengthy window to overlap with an auto-save -- This message was sent by Atlassian JIRA (v6.3.4#6332)