[
https://issues.apache.org/jira/browse/CASSANDRA-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15296788#comment-15296788
]
Alex Petrov commented on CASSANDRA-7190:
----------------------------------------
bq. I think you're referring to MVs being built and/or having pending updates
in some batch log.
[~snazy] I mostly meant that since this ticket is about snapshot manifest
restore (and the fact that if the table does not exist, one has to re-create it
manually), when creating a snapshot, snapshot of materialised view is created
in the same way as table snapshot. In json format we could've simply dumped the
`isView` flag to re-create it, since we decided to go the CQL way, the schema
definition for MV will be same as the "normal" table. When the view is created,
we announce both schema change and creation of the view. Having just the table
re-created will make the view to normal table and it's relation to it's base
table will get lost.
> Add schema to snapshot manifest
> -------------------------------
>
> Key: CASSANDRA-7190
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7190
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Reporter: Jonathan Ellis
> Assignee: Alex Petrov
> Priority: Minor
> Labels: lhf
> Fix For: 3.x
>
>
> followup from CASSANDRA-6326
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
