[
https://issues.apache.org/jira/browse/HBASE-15790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15302724#comment-15302724
]
Matteo Bertozzi commented on HBASE-15790:
-----------------------------------------
yeah, it will throw exception. any idea on how change it?
I basically want to prevent the ability to bulkload files hbase is not able to
interact with.
as enis mentioned SecureBulkLoad is the way to go since it works in both secure
and unsecure way, but some people still don't use it since it is something that
we still have to enable by hand.
> 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)
