cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "T Jake Luciani (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9927) Security for MaterializedViews
Date Thu, 06 Aug 2015 14:01:05 GMT

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

T Jake Luciani commented on CASSANDRA-9927:
-------------------------------------------

I don't think they inherit the base tables permissions currently.  

I would be trivial to add the current role to the MV at the time of MV creation.  However
it's not clear if you want the role pinned so any changes to the base affect the view.  That
would go against the let users add different roles for different views.  



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

Mime
View raw message