You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2015/08/05 22:14:04 UTC
[jira] [Commented] (CASSANDRA-9927) Security for MaterializedViews
[ https://issues.apache.org/jira/browse/CASSANDRA-9927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14658812#comment-14658812 ]
Jonathan Ellis commented on CASSANDRA-9927:
-------------------------------------------
Why can't we just inherit base table permissions for 3.0?
> 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)