hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerry He (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13701) Consolidate SecureBulkLoadEndpoint into HBase core as default for bulk load
Date Thu, 23 Jun 2016 18:17:16 GMT

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

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

The approach will be to rename SecureBulkLoadEndpoint to SecureBulkLoadManager and put it
on HRegionServer.  The bulk of its code logic will be un-touched. 
RSRpcServices will call into this SecureBulkLoadManager.
SecureBulkLoadEndpoint will be kept and emptied to just call into SecureBulkLoadManager held
on the HRegionServer.
New client will call to RSRpcServices.  Old client can still call into SecureBulkLoadEndpoint.

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

Mime
View raw message