[
https://issues.apache.org/jira/browse/CASSANDRA-9921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14680258#comment-14680258
]
Carl Yeksigian commented on CASSANDRA-9921:
-------------------------------------------
The idea of this is to remove the entries for MV from the Tables schema, and
move necessary properties to the MV schema instead. Both the MV and the Tables
would live at the Keyspace level, and MVManager would be moved from the CFS to
the Keyspace.
- Copy properties from the {{Schema.tables}} table to the
{{Schema.materialized_views}} table, remove {{MaterializedView}} from
{{CFMetaData.Flag}}; this can be easily done using the changes to factor out
{{TableParams}} by [~iamaleksey]
- Remove the columns from the schema table; we can reference the
{{Schema.columns}} table instead; add an {{includeAll}} flag to indicate
whether all columns are included or not
- Change the base table reference to be the ID instead of name, to prevent
referencing the wrong table (should address [~benedict]'s
[comment|https://issues.apache.org/jira/browse/CASSANDRA-6477?focusedCommentId=14662980&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14662980])
- Move {{MVManager}} to {{Keyspace}} instead of CFS
- When a Keyspace is instantiated, MV's should be last to be created, so they
can resolve the Tables they reference
> Combine MV schema definition with MV table definition
> -----------------------------------------------------
>
> Key: CASSANDRA-9921
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9921
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Carl Yeksigian
> Assignee: Carl Yeksigian
> Labels: client-impacting, materializedviews
> Fix For: 3.0 beta 1
>
>
> Prevent MV from reusing {{system_schema.tables}} and instead move those
> properties into the {{system_schema.materializedviews}} table to keep them
> separate entities.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
