[
https://issues.apache.org/jira/browse/CASSANDRA-8163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14550527#comment-14550527
]
Jonathan Ellis edited comment on CASSANDRA-8163 at 5/19/15 2:44 PM:
--------------------------------------------------------------------
If this is a breaking API change, we'll have to do it in 4.0 if it doesn't make
3.0. (But I'm not tagging it for 3.0 b1 since I'd prefer to reserve that for
must-have tickets.)
was (Author: jbellis):
Since this is a breaking API change, we'll have to do it in 4.0 if it doesn't
make 3.0. (But I'm not tagging it for 3.0 b1 since I'd prefer to reserve that
for must-have tickets.)
> 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)
