[
https://issues.apache.org/jira/browse/CASSANDRA-9927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14658990#comment-14658990
]
Aleksey Yeschenko commented on CASSANDRA-9927:
----------------------------------------------
bq. Why can't we just inherit base table permissions for 3.0?
That was the initial suggestion, still in CASSANDRA-6477 comments. Jake raised
a valid point that a user might want to grant access to the view that is a
subset of the columns in the base to more users (if a view doesn't have
anything sensitive, but the base table does).
What do we want to do in the long term?
> Security for MaterializedViews
> ------------------------------
>
> Key: CASSANDRA-9927
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9927
> Project: Cassandra
> Issue Type: Task
> Reporter: T Jake Luciani
> Labels: materializedviews
> Fix For: 3.0 beta 1
>
>
> We need to think about how to handle security wrt materialized views. Since
> they are based on a source table we should possibly inherit the same security
> model as that table.
> However I can see cases where users would want to create different security
> auth for different views. esp once we have CASSANDRA-9664 and users can
> filter out sensitive data.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
