[
https://issues.apache.org/jira/browse/CASSANDRA-9736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16076117#comment-16076117
]
ZhaoYang commented on CASSANDRA-9736:
-------------------------------------
Semantic for {{alter view}} :
# support alter view
## if view is wildcard, eg. {{select *}}
### view cannot add column. all columns are selected
### view can drop column. eg. change from {{*}} to {{a,b}} but it may confuse
user later when adding new column to base and not included in view.
### view primary key cannot be rename, pls rename base table instead
## if view is not wildcard, eg. {{select a,b,c}}
### view can drop columns except for last remaining column
### view can add columns except for base's static column
## cannot drop restricted column(eg. {{where a=2}}) on view, because that
needs rebuild view data. dropping view and recreating view is better
## support altering view's {{table_options}}, eg. compaction, etc.
## view primary key cannot be altered
# support drop column from base if view doesn't select or restrict those columns
> Add alter statement for MV
> --------------------------
>
> Key: CASSANDRA-9736
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9736
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Carl Yeksigian
> Assignee: ZhaoYang
> Labels: materializedviews
> Fix For: 4.x
>
>
> {{ALTER MV}} would allow us to drop columns in the base table without first
> dropping the materialized views, since we'd be able to later drop columns in
> the MV.
> Also, we should be able to add new columns to the MV; a new builder would
> have to run to copy the values for these additional columns.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
