[
https://issues.apache.org/jira/browse/HBASE-15790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15302618#comment-15302618
]
Enis Soztutar commented on HBASE-15790:
---------------------------------------
bq. SecureBulkLoadEndpoint seems to always do the chmod 777. so we are good in
that case even if the files are owned by someone that is not hbase.
There was an issue to make SBLE to be the default way for BL even in unsecure
setups. Even in unsecure setups, the SBLE does the "correct" thing in terms of
passing the file down to RS. Maybe we should finish the jira that wanted to
refactor SBLE to be the default method (meanly replacing the need for the
coprocessor).
> Force "hbase" ownership on bulkload
> -----------------------------------
>
> Key: HBASE-15790
> URL: https://issues.apache.org/jira/browse/HBASE-15790
> Project: HBase
> Issue Type: Bug
> Components: regionserver
> Affects Versions: 2.0.0, 1.2.1, 1.1.4, 0.98.19
> Reporter: Matteo Bertozzi
> Assignee: Matteo Bertozzi
> Priority: Minor
> Attachments: HBASE-15790-v0.patch, HBASE-15790-v1.patch,
> HBASE-15790-v2.patch, HBASE-15790-v3.patch
>
>
> When a user different than "hbase" bulkload files, in general we end up with
> files owned by a user different than hbase. sometimes this causes problems
> with hbase not be able to move files around archiving/deleting.
> A simple solution is probably to change the ownership of the files to "hbase"
> during bulkload.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
