Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EDDAD181DB for ; Fri, 7 Aug 2015 22:46:47 +0000 (UTC) Received: (qmail 61785 invoked by uid 500); 7 Aug 2015 22:46:47 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 61754 invoked by uid 500); 7 Aug 2015 22:46:47 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 61743 invoked by uid 99); 7 Aug 2015 22:46:47 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Aug 2015 22:46:47 +0000 Date: Fri, 7 Aug 2015 22:46:47 +0000 (UTC) From: "Aleksey Yeschenko (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-9927) Security for MaterializedViews MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-9927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14662600#comment-14662600 ] Aleksey Yeschenko commented on CASSANDRA-9927: ---------------------------------------------- The doc is for 2.0 and 2.1, it says so in the title. In 2.2 and 3.0 that is no longer true. What base permissions we should require for {{CREATE MV}} is the only minor detail I'm not certain about. Maybe we should just treat them as indexes for now and require {{ALTER}} on the base table for both {{CREATE MV}} and {{DROP MV}}. [~beobal] ? > Security for MaterializedViews > ------------------------------ > > Key: CASSANDRA-9927 > URL: https://issues.apache.org/jira/browse/CASSANDRA-9927 > Project: Cassandra > Issue Type: Task > Reporter: T Jake Luciani > Assignee: Paulo Motta > 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)