[
https://issues.apache.org/jira/browse/CASSANDRA-9921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14743861#comment-14743861
]
Adam Holmberg commented on CASSANDRA-9921:
------------------------------------------
Thanks Aleksey. I'm still struggling a bit with this data model. Right now we
get both keyspace and table change events pushed when a view is added. I
understand we can't have view events yet because of protocol limitations. With
just the base table name, we're unable to selectively query views for the
table. One suggestion would be to cluster by {{base_table_name}} now that it's
available:
{code}
CREATE TABLE system_schema.views (... PIMARY KEY (keyspace_name,
base_table_name, view_name))
{code}
Even with that, we're still faced with another query phase to get the
{{system_schema.columns}} belonging to the views, once they're known. Are we
just going to live with that until view events come along?
> 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.0 rc1
>
> Attachments: 9921-unit-test.txt
>
>
> 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)
