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