[jira] [Commented] (CASSANDRA-13180) Better handling of missing entries in system_schema.columns during startup

["Aleksey Yeschenko (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-13180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15851503#comment-15851503 ] 

Aleksey Yeschenko commented on CASSANDRA-13180:
-----------------------------------------------

+1

> Better handling of missing entries in system_schema.columns during startup
> --------------------------------------------------------------------------
>
>                 Key: CASSANDRA-13180
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13180
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Distributed Metadata
>            Reporter: Tyler Hobbs
>            Assignee: Tyler Hobbs
>             Fix For: 3.0.x, 3.x
>
>
> Like the error in CASSANDRA-12213 and CASSANDRA-12165, it's possible for {{system_schema.keyspaces}} and {{tables}} to contain entries for a table while {{system_schema.columns}} has none.  This produces an error during startup, and there's no way for a user to recover from this without restoring from backups.
> Although this has been seen in the wild on one occasion, the cause is still not entirely known.  (It may be due to a concurrent DROP TABLE and ALTER TABLE where a table property is altered.)  Until we know the root cause, it makes sense to give users a way to recover from that situation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)