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 21D7E18962 for ; Tue, 19 May 2015 13:59:06 +0000 (UTC) Received: (qmail 13390 invoked by uid 500); 19 May 2015 13:59:01 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 13353 invoked by uid 500); 19 May 2015 13:59:01 -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 13341 invoked by uid 99); 19 May 2015 13:59:00 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 May 2015 13:59:00 +0000 Date: Tue, 19 May 2015 13:59:00 +0000 (UTC) From: "Aleksey Yeschenko (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (CASSANDRA-8163) Re-introduce DESCRIBE permission 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-8163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14550333#comment-14550333 ] Aleksey Yeschenko edited comment on CASSANDRA-8163 at 5/19/15 1:58 PM: ----------------------------------------------------------------------- -Can we, for 2.2, just introduce the permission to the enum, and have it be a no-op?- -I don't want us to break the API again in 3.0.- Scratch that, we already have it in the enum, for roles. Sorry for the confusion. was (Author: iamaleksey): Can we, for 2.2, just introduce the permission to the enum, and have it be a no-op? I don't want us to break the API again in 3.0. > Re-introduce DESCRIBE permission > -------------------------------- > > Key: CASSANDRA-8163 > URL: https://issues.apache.org/jira/browse/CASSANDRA-8163 > Project: Cassandra > Issue Type: Improvement > Reporter: Vishy Kasar > Priority: Minor > Fix For: 3.x > > > We have a cluster like this: > project1_keyspace > table101 > table102 > project2_keyspace > table201 > table202 > We have set up following users and grants: > project1_user has all access to project1_keyspace > project2_user has all access to project2_keyspace > However project1_user can still do a 'describe schema' and get the schema for project2_keyspace as well. We do not want project1_user to have any knowledge for project2 in any way (cqlsh/java-driver etc) . -- This message was sent by Atlassian JIRA (v6.3.4#6332)