[
https://issues.apache.org/jira/browse/CASSANDRA-9927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14680875#comment-14680875
]
Paulo Motta commented on CASSANDRA-9927:
----------------------------------------
Updated branches with suggested modifications:
* [3.0
patch|https://github.com/apache/cassandra/compare/cassandra-3.0...pauloricardomg:9927-3.0]
* [trunk
patch|https://github.com/apache/cassandra/compare/trunk...pauloricardomg:9927-trunk]
Materialized views authentication dtests available here:
[PR451|https://github.com/riptano/cassandra-dtest/pull/451]
When ready, tests will be available here:
* [3.0
dtest|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-9927-3.0-dtest/]
* [3.0
testall|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-9927-3.0-testall/]
* [trunk
dtest|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-9927-trunk-dtest/]
* [trunk
testall|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-9927-trunk-testall/]
> 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)
