[
https://issues.apache.org/jira/browse/HBASE-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13270635#comment-13270635
]
Andrew Purtell commented on HBASE-5342:
---------------------------------------
@Matteo,
To maintain compatibility in HBase aka Hadoop RPC as it currently works, you
must insure:
- The new methods must be placed after all others in the interface. If the
order of existing methods in the interface changes, it won't work.
- Do not change VERSION in VersionedProtocols (which CoprocessorProtocol
inherits from). This doesn't allow backwards compatibility, it tells the client
to go away if different. We can use it to fast fail incompatible clients after
a deprecation is complete but not during the transition.
- Then, if the new methods are not available, on the client side you can catch
NoSuchMethodException from the remote and use an alternate API strategy.
As you can imagine, it is a great thing we are migrating all of our RPC
protocols to protobufs for 0.96+, it has a cross-version story that avoids
kludges like the above. Unfortunately, the above is currently necessary.
> Grant/Revoke global permissions
> -------------------------------
>
> Key: HBASE-5342
> URL: https://issues.apache.org/jira/browse/HBASE-5342
> Project: HBase
> Issue Type: Sub-task
> Reporter: Enis Soztutar
> Assignee: Matteo Bertozzi
> Attachments: HBASE-5342-draft.patch, HBASE-5342-v0.patch,
> HBASE-5342-v1.patch, HBASE-5342-v2.patch
>
>
> HBASE-3025 introduced simple ACLs based on coprocessors. It defines
> global/table/cf/cq level permissions. However, there is no way to
> grant/revoke global level permissions, other than the hbase.superuser conf
> setting.
--
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
