You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jack Krupansky (JIRA)" <ji...@apache.org> on 2015/07/29 22:47:05 UTC
[jira] [Issue Comment Deleted] (CASSANDRA-9927) Security for
MaterializedViews
[ https://issues.apache.org/jira/browse/CASSANDRA-9927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jack Krupansky updated CASSANDRA-9927:
--------------------------------------
Comment: was deleted
(was: The CQL.textile for MV still shows parentheses being required around the selection list, which is not the case in SELECT.)
> Security for MaterializedViews
> ------------------------------
>
> Key: CASSANDRA-9927
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9927
> Project: Cassandra
> Issue Type: Task
> Reporter: T Jake Luciani
> 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)