You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Stu Hood (JIRA)" <ji...@apache.org> on 2010/08/28 08:35:54 UTC

[jira] Issue Comment Edited: (CASSANDRA-1320) Convert AccessLevel to Set

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

Stu Hood edited comment on CASSANDRA-1320 at 8/28/10 2:34 AM:
--------------------------------------------------------------

Converts AccessLevel to EnumSet<Permission> (with semantics from CASSANDRA-1271), but does not add or remove any authorize() calls. 1271 will add the new resources, and probably add a few authorize calls.

      was (Author: stuhood):
    Converts AccessLevel to EnumSet<Permission> (with semantics from CASSANDRA-1320), but does not add or remove any authorize() calls. 1320 will add the new resources, and probably add a few authorize calls.
  
> Convert AccessLevel to Set<Permission>
> --------------------------------------
>
>                 Key: CASSANDRA-1320
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1320
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Stu Hood
>            Assignee: Stu Hood
>             Fix For: 0.7.0
>
>         Attachments: 0001-Remove-AccessLevel-from-the-client-API.patch, 0002-Convert-AccessLevel-to-Set-Permission.patch, 0003-Convert-to-Permission-usage-in-Thrift-Avro-servers.patch
>
>
> Level based permissions are very limiting, and are likely to become restrictive. The original reasoning behind using levels seems to be that Thrift didn't allow an easy way to specify bitset permissions, but a Set<Enums> works equally well.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.