[
https://issues.apache.org/jira/browse/CASSANDRA-8082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14165049#comment-14165049
]
Aleksey Yeschenko commented on CASSANDRA-8082:
----------------------------------------------
[~johnny15676] neither. But we'll consider it when rethinking Auth APIs for
CASSANDRA-7653 in 3.0 and maybe add extra permissions for functions/types/users
(CASSANDRA-7216).
> Support finer grained Modify CQL permissions
> --------------------------------------------
>
> Key: CASSANDRA-8082
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8082
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Johnny Miller
>
> Currently CQL permissions are grouped as:
> ALL - All statements
> ALTER - ALTER KEYSPACE, ALTER TABLE, CREATE INDEX, DROP INDEX
> AUTHORIZE - GRANT, REVOKE
> CREATE - CREATE KEYSPACE, CREATE TABLE
> DROP - DROP KEYSPACE, DROP TABLE
> MODIFY - INSERT, DELETE, UPDATE, TRUNCATE
> SELECT -SELECT
> The MODIFY permission is too wide. There are plenty scenarios where a user
> should not be to DELETE and TRUNCATE a table but should be able to INSERT and
> UPDATE.
> It would be great if Cassandra could either support defining permissions
> dynamically or have additional finer grained MODIFY related permissions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
