Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 6 Jul 2016 20:29:11 +0000 (UTC)
From: "Jerry He (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12830356.1431735837000.41183.1467836951014@Atlassian.JIRA>
In-Reply-To: <JIRA.12830356.1431735837000@Atlassian.JIRA>
References: <JIRA.12830356.1431735837000@Atlassian.JIRA> <JIRA.12830356.1431735837990@arcas>
Subject: [jira] [Commented] (HBASE-13701) Consolidate SecureBulkLoadEndpoint
 into HBase core as default for bulk load
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 06 Jul 2016 20:29:13 -0000


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

Jerry He commented on HBASE-13701:
----------------------------------

There is another point I want to raise here.

The hbase.bulkload.staging.dir defaults to hbase.fs.tmp.dir which then defaults to
{code}
public static final String DEFAULT_TEMPORARY_HDFS_DIRECTORY = "/user/"
      + System.getProperty("user.name") + "/hbase-staging";
{code}

This default would have problem on local file system standalone case.

I am thinking about bringing hbase.bulkload.staging.dir to be under hbase.rootdir.  We are bringing secure bulkload to the core. It makes sense to bring the staging dir under core control as well, instead of an optional property.

Any concern?


> Consolidate SecureBulkLoadEndpoint into HBase core as default for bulk load
> ---------------------------------------------------------------------------
>
>                 Key: HBASE-13701
>                 URL: https://issues.apache.org/jira/browse/HBASE-13701
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Jerry He
>            Assignee: Jerry He
>             Fix For: 2.0.0
>
>         Attachments: HBASE-13701-v1.patch, HBASE-13701-v2.patch, HBASE-13701-v3.patch, HBASE-13701-v4.patch
>
>
> HBASE-12052 makes SecureBulkLoadEndpoint work in a non-secure env to solve HDFS permission issues.
> We have encountered some of the permission issues and have to use this SecureBulkLoadEndpoint to workaround issues.
> We should  probably consolidate SecureBulkLoadEndpoint into HBase core as default for bulk load since it is able to handle both secure Kerberos and non-secure cases.
> Maintaining two versions of bulk load implementation is also a cause of confusion, and having to explicitly set it is also inconvenient.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)