You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2015/09/02 00:51:46 UTC

[jira] [Commented] (CASSANDRA-9921) Combine MV schema definition with MV table definition

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

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

Looks all right on a very high level. Will take a deeper look tomorrow.

Timing-wise, though, this might end up going to rc1, because of a necessary round-trip with the drivers team once we are done here.

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