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 Fri, 11 Sep 2015 21:17:46 GMT


Aleksey Yeschenko commented on CASSANDRA-9921:

bq. Would it be feasible to include base_table_name in the view metadata? Not having that
adds complexity to clients because nothing is indexed using base_table_id.

Yes. In fact, Tyler was going to do so in CASSANDRA-9664. But we can add it here too, so that
there is one fewer drivers roundtrip. Will do so.

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

View raw message