[
https://issues.apache.org/jira/browse/HBASE-21356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16658855#comment-16658855
]
Zheng Hu edited comment on HBASE-21356 at 10/22/18 10:32 AM:
-------------------------------------------------------------
Some user may set the source bulk load dir to 777, it's OK and the rs works
fine. but put the rs's hfile in the risk of deleting by accident... So, in our
cluster, we let the HBase user add HDFS ACL for hbase_srv, then only the owner
and hbase_srv has the write permission of the hfile... but some user may forget
to add write ACL for hbase_srv, so I open an issue to address this.
was (Author: openinx):
Some user may set the source bulk load dir to 777, it's OK and the rs works
fine. but put the rs's hfile in the risk of deleting by accident... So, in our
cluster, we let the HBase user add HDFS ACL for hbase_srv, then only the owner
and hbase_srv has the write permission of the hfile.
> bulkLoadHFile API should ensure that rs has the source hfile's write
> permission
> -------------------------------------------------------------------------------
>
> Key: HBASE-21356
> URL: https://issues.apache.org/jira/browse/HBASE-21356
> Project: HBase
> Issue Type: Bug
> Reporter: Zheng Hu
> Assignee: Zheng Hu
> Priority: Major
> Fix For: 3.0.0, 2.2.0, 2.0.3, 2.1.2
>
> Attachments: HBASE-21356.v1.patch
>
>
> If the rs bulk load a HFile but has no write permission of it, we can read &
> compact the hfile, but after the compaction finished, the HFile willl be
> moved to archive directory, the HFileCleaner won't has permission to delete,
> then the HFile will always be keep in HDFS.
> Need check the file's write permission when run bulkLoadHFile at server side,
> if no write permission, then reject.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
