cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Zlatanov (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-973) new AccessLevel needed above FULL for schema modifications
Date Mon, 12 Apr 2010 18:19:50 GMT

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

Ted Zlatanov commented on CASSANDRA-973:
----------------------------------------

I know, FULL is ambiguous.  I proposed making each capability a bitmask but Thrift doesn't
handle that well.  So either we merge schema management into FULL, which is not nice, or we
make a new level to represent read+write+delete, or we create this new AccessLevel.

I like Todd's recommendation of "MANAGE" since it can be used for other administration capabilities
as well.

Gary, should I produce a patch or is there a reason not to make the change?

> new AccessLevel needed above FULL for schema modifications
> ----------------------------------------------------------
>
>                 Key: CASSANDRA-973
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-973
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Ted Zlatanov
>
> AccessLevel.FULL is for read+write+delete, but modifying the schema with the new Thrift
functions should require a higher level.  Maybe AccessLevel.SCHEMA?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message