[
https://issues.apache.org/jira/browse/HBASE-11008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13972123#comment-13972123
]
Aleksandr Shulman commented on HBASE-11008:
-------------------------------------------
We should be careful to consider what workflows we might disrupt with this
change. Specifically, we should consider while the user is upgrading (rolling
upgrade) and after the upgrade is complete.
Bulk loading is something that users can expect to do while a rolling upgrade
is going on. If some regionservers begin enforcing a more restrictive
requirement, then it will cause issues. If we choose to make it more
restrictive, we should document any changes we should make to the ACL table in
order to allow the upgrade to go smoothly.
If we choose to make it less restrictive (e.g. allow admin permissions to users
with create), then we have to acknowledge that the ACL semantics have changed
and document that appropriately.
> Align bulk load, flush, and compact to require Action.CREATE
> ------------------------------------------------------------
>
> Key: HBASE-11008
> URL: https://issues.apache.org/jira/browse/HBASE-11008
> Project: HBase
> Issue Type: Improvement
> Components: security
> Reporter: Jean-Daniel Cryans
> Assignee: Jean-Daniel Cryans
> Fix For: 0.99.0, 0.98.2, 0.96.3, 0.94.20
>
> Attachments: HBASE-11008.patch
>
>
> Over in HBASE-10958 we noticed that it might make sense to require
> Action.CREATE for bulk load, flush, and compact since it is also required for
> things like enable and disable.
> This means the following changes:
> - preBulkLoadHFile goes from WRITE to CREATE
> - compact/flush go from ADMIN to ADMIN or CREATE
--
This message was sent by Atlassian JIRA
(v6.2#6252)
