cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9921) Combine MV schema definition with MV table definition
Date Mon, 10 Aug 2015 15:36:46 GMT


Aleksey Yeschenko commented on CASSANDRA-9921:

Could you outline "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"
in more detail before going on with the implementation? I agree in general, just want to make
sure that we agree on specifics as well.

Overall, this is all good - you should go ahead.

> Combine MV schema definition with MV table definition
> -----------------------------------------------------
>                 Key: CASSANDRA-9921
>                 URL:
>             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

View raw message