Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 29 Jul 2015 20:47:05 +0000 (UTC)
From: "Jack Krupansky (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12850047.1438199512000.323802.1438202825123@Atlassian.JIRA>
In-Reply-To: <JIRA.12850047.1438199512000@Atlassian.JIRA>
References: <JIRA.12850047.1438199512000@Atlassian.JIRA>
 <JIRA.12850047.1438199512721@arcas>
Subject: [jira] [Commented] (CASSANDRA-9927) Security for MaterializedViews
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jack Krupansky commented on CASSANDRA-9927:
-------------------------------------------

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)