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

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

I have had TestHRegionServerBulkLoadWithOldClient running 20 times in a loop 
with master branch.  All passed.

{code}
Running 
org.apache.hadoop.hbase.regionserver.TestHRegionServerBulkLoadWithOldClient
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 92.146 sec - in 
org.apache.hadoop.hbase.regionserver.TestHRegionServerBulkLoadWithOldClient
Running 
org.apache.hadoop.hbase.regionserver.TestHRegionServerBulkLoadWithOldClient
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 88.669 sec - in 
org.apache.hadoop.hbase.regionserver.TestHRegionServerBulkLoadWithOldClient
...
{code}

I am not sure why it is on the flaky list.  Let's try it out of the flaky list, 
I think.

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

Reply via email to