You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ben Laplanche (JIRA)" <ji...@apache.org> on 2015/01/06 12:06:35 UTC

[jira] [Commented] (CASSANDRA-8163) Re-introduce DESCRIBE permission

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

Ben Laplanche commented on CASSANDRA-8163:
------------------------------------------

The ability for users to see the table names for other users keyspaces is blocking us from using a cluster in a multi-tenant setup, which for some clients and the nature of their work can be prohibitive in using Cassandra. 

> 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
>
> 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)