You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Matteo Bertozzi (JIRA)" <ji...@apache.org> on 2016/07/20 04:38:20 UTC

[jira] [Updated] (HBASE-15790) Force "hbase" ownership on bulkload

     [ https://issues.apache.org/jira/browse/HBASE-15790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matteo Bertozzi updated HBASE-15790:
------------------------------------
    Resolution: Won't Fix
        Status: Resolved  (was: Patch Available)

closing since HBASE-13701 went in. the SecureBulk in core will avoid the problem in the first place

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