[ https://issues.apache.org/jira/browse/CASSANDRA-9927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14662676#comment-14662676 ]
Paulo Motta commented on CASSANDRA-9927: ---------------------------------------- Updated branches with suggested modifications: * [3.0 patch|https://github.com/pauloricardomg/cassandra/tree/9927-3.0] * [trunk patch|https://github.com/pauloricardomg/cassandra/tree/9927-trunk] Updated policies: * {{CREATE MATERIALIZED VIEW}}: {{ALTER}} and {{SELECT}} permissions on base table or parent keyspace. * {{ALTER MATERIALIZED VIEW}}: {{ALTER}} permission on base table or parent keyspace. * {{DROP MATERIALIZED VIEW}}: {{DROP}} permission on base table or parent keyspace. * {{SELECT}}: {{SELECT}} permissions on base table or parent keyspace. Tests will be available shortly on the following links: * [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)