cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9921) Combine MV schema definition with MV table definition
Date Fri, 04 Sep 2015 16:18:46 GMT

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

Aleksey Yeschenko commented on CASSANDRA-9921:
----------------------------------------------

Pushed some nits to the same branch. All naming-related. Schema structure is good to go. [~aholmber]
and [~omichallat] - would be nice if you could start adding support now, on top of that branch.

Otherwise going to need a couple passes to make sure nothing go broken here - handling of
DDL changes in particular, but everything mostly looks ok to me.

> 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
>
>
> 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)

Mime
View raw message