Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 26 May 2016 23:18:12 +0000 (UTC)
From: "Jerry He (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12965698.1462562992000.310174.1464304692869@Atlassian.JIRA>
In-Reply-To: <JIRA.12965698.1462562992000@Atlassian.JIRA>
References: <JIRA.12965698.1462562992000@Atlassian.JIRA> <JIRA.12965698.1462562992080@arcas>
Subject: [jira] [Commented] (HBASE-15790) Force "hbase" ownership on
 bulkload
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 26 May 2016 23:18:14 -0000


    [ https://issues.apache.org/jira/browse/HBASE-15790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15303139#comment-15303139 ] 

Jerry He commented on HBASE-15790:
----------------------------------

Could you give a specific example of the problem on the permissions from hbase bulk load.

Yes. The SecureBulkLoad is the way to go. I have a JIRA to get it unified and be default HBASE-13701. I think I should start working on it ...

> 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)