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 6D1E318C72 for ; Mon, 10 Aug 2015 20:30:47 +0000 (UTC) Received: (qmail 26855 invoked by uid 500); 10 Aug 2015 20:30:47 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 26823 invoked by uid 500); 10 Aug 2015 20:30: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 26812 invoked by uid 99); 10 Aug 2015 20:30:46 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Aug 2015 20:30:46 +0000 Date: Mon, 10 Aug 2015 20:30:46 +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=14680714#comment-14680714 ] Aleksey Yeschenko commented on CASSANDRA-9927: ---------------------------------------------- This is the desired logic, thank you. That said, it doesn't build when applied to current cassandra-3.0 (can you fix and rebase?) Also the tests don't build. {{CQLAuthTester}} is missing, and, in general, {{MaterializedViewAuthorizationTest}} doesn't belong where it was put. All auth test currently belong to dtests, [here|https://github.com/riptano/cassandra-dtest/blob/master/auth_test.py]. Can you please convert the tests to dtests, where the other auth tests are? > 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)