cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stu Hood (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CASSANDRA-1320) Convert AccessLevel to Set<Permission>
Date Mon, 26 Jul 2010 19:22:15 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Stu Hood updated CASSANDRA-1320:
--------------------------------

    Attachment: 0001-Avro-and-Thrift-interface-changes.patch
                0002-Convert-AccessLevel-to-Set-Permission.patch
                0003-Use-Permission-checks-rather-than-AccessLevel-checks.patch

Applies on top of CASSANDRA-1237, and converts AccessLevel to Set<Permission>.

We'd like to get this change into 0.7-beta, since it changes the disk format for KSMetaData.

> 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 beta 1
>
>         Attachments: 0001-Avro-and-Thrift-interface-changes.patch, 0002-Convert-AccessLevel-to-Set-Permission.patch,
0003-Use-Permission-checks-rather-than-AccessLevel-checks.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.


Mime
View raw message