[
https://issues.apache.org/jira/browse/CASSANDRA-8082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14164863#comment-14164863
]
Johnny Miller edited comment on CASSANDRA-8082 at 10/9/14 7:29 AM:
-------------------------------------------------------------------
[~iamaleksey] [~slebresne] I think TRUNCATE is the main point of concern. I
understand the constraints around the upserts/deletes and the difficulty with
doing anything on that, but if we could do something on TRUNCATE it would still
help. Can we re-open this ticket or should I create a new one?
was (Author: johnny15676):
[~iamaleksey] [~salleman] I think TRUNCATE is the main point of concern. I
understand the constraints around the upserts/deletes and the difficulty with
doing anything on that, but if we could do something on TRUNCATE it would still
help. Can we re-open this ticket or should I create a new one?
> 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)
