hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matteo Bertozzi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-5449) Support for wire-compatible security functionality
Date Sat, 18 Aug 2012 19:19:38 GMT

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

Matteo Bertozzi updated HBASE-5449:
-----------------------------------

    Attachment: HBASE-5449-v0.patch

First draft of protobuf conversion, 
patch without compiled protobuf available at https://reviews.apache.org/r/6689/

This patch just switch the current serialization code to protobuf.

but I think that we can remove, or change, some stuff during this conversion.
Currently there're 3 classes
 * Permission
 * TablePermission : Permission
 * UserPermission : TablePermission

UserPermission is the "public" class used by the shell to describe a user permission...
Can be a global permission that means just username + actions (RWXCA) or a table permission
username + actions + table + cf + qualifier..

Permission is never used directly (there's just one ref in the shell, but just for printing)

TablePermission is the main class used, and The znode contains a ListMultimap (user: [table
permission])

Maybe we can remove the inheritance UserPermission -> TablePermission -> Permission,
change the Permission in an Abstract class and maybe something else...

any thoughts?
                
> Support for wire-compatible security functionality
> --------------------------------------------------
>
>                 Key: HBASE-5449
>                 URL: https://issues.apache.org/jira/browse/HBASE-5449
>             Project: HBase
>          Issue Type: Sub-task
>          Components: ipc, master, migration, regionserver
>            Reporter: Todd Lipcon
>            Assignee: Matteo Bertozzi
>         Attachments: HBASE-5449-v0.patch
>
>


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

        

Mime
View raw message