[
https://issues.apache.org/jira/browse/CASSANDRA-9921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tyler Hobbs updated CASSANDRA-9921:
-----------------------------------
Attachment: 9921-unit-test.txt
It looks like the current patch (Aleksey's branch) doesn't handle renaming
columns when the SELECT is on specific columns instead of {{SELECT *}}. I've
attached a unit test that reproduces the issue.
> 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
>
> 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
(v6.3.4#6332)
