cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9927) Security for MaterializedViews
Date Fri, 07 Aug 2015 22:46:47 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-9927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14662600#comment-14662600
] 

Aleksey Yeschenko commented on CASSANDRA-9927:
----------------------------------------------

The doc is for 2.0 and 2.1, it says so in the title. In 2.2 and 3.0 that is no longer true.

What base permissions we should require for {{CREATE MV}} is the only minor detail I'm not
certain about. Maybe we should just treat them as indexes for now and require {{ALTER}} on
the base table for both {{CREATE MV}} and {{DROP MV}}. [~beobal] ?

> 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)

Mime
View raw message