cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carl Yeksigian (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9921) Combine MV schema definition with MV table definition
Date Mon, 10 Aug 2015 15:44:46 GMT

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

Carl Yeksigian commented on CASSANDRA-9921:
-------------------------------------------

Right now we're storing all of the columns in the {{Schema.materialized_views}} table, because
we don't use {{Schema.columns}} when initializing the MV. This means that we have a copy of
the column definitions (Primary, Clustering, and "Included") in the MV definition, and we
also have them in {{Schema.columns}}. We can remove that duplication, since all of the information
we'd be using is already included in columns, except for whether this was a {{SELECT *}} query
or not. That additional piece of information can be captured more succinctly as a boolean
(includeAll) on the MV schema table.

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

Mime
View raw message