cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-9927) Security for MaterializedViews
Date Thu, 06 Aug 2015 15:59:05 GMT

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

Jonathan Ellis edited comment on CASSANDRA-9927 at 8/6/15 3:58 PM:
-------------------------------------------------------------------

I'm happy with leaving MV permissions to be set explicitly.  Inheriting base permissions is
definitely not the right thing in all situations.

NB: Aleksey pointed out that we do to require SELECT on the base table when CREATEing an MV.


was (Author: jbellis):
I'm happy with leaving MV permissions explicity.  Inheriting base permissions is definitely
not the right thing in all situations.

NB: Aleksey pointed out that we do to require SELECT on the base table when CREATEing an MV.

> 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