[
https://issues.apache.org/jira/browse/CASSANDRA-9927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14680941#comment-14680941
]
Aleksey Yeschenko commented on CASSANDRA-9927:
----------------------------------------------
Committed as
[1a9286c07a5c168df677da9d6be7178d087ea005|https://github.com/apache/cassandra/commit/1a9286c07a5c168df677da9d6be7178d087ea005]
to cassandra-3.0 and merged into trunk, thanks.
> Security for MaterializedViews
> ------------------------------
>
> Key: CASSANDRA-9927
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9927
> Project: Cassandra
> Issue Type: Task
> Reporter: T Jake Luciani
> Assignee: Paulo Motta
> 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)
