[jira] [Commented] (HBASE-13701) Consolidate SecureBulkLoadEndpoint into HBase core as default for bulk load

["Umesh Agashe (JIRA)" <ji...@apache.org>]

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

Umesh Agashe commented on HBASE-13701:
--------------------------------------

Hi [~jerryhe],

I am looking into fixing some of the flaky tests here: https://builds.apache.org/job/HBASE-Find-Flaky-Tests/lastSuccessfulBuild/artifact/dashboard.html. One of the tests is TestHRegionServerBulkLoadWithOldClient.java. I would appreciate if you can give me some pointers regarding why it could be failing and how to fix it.

Thanks, Umesh

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