[
https://issues.apache.org/jira/browse/HBASE-13701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15349092#comment-15349092
]
Jerry He commented on HBASE-13701:
----------------------------------
Put it on Review Board.
Again, this is a summary.
1. SecureBulkLoadEndpoint becomes SecureBulkLoadManager on the HRegionServer.
Most of the code logic to do the bulk load is untouched. Only cleaned up the
coprocessor endpoint related code.
2. SecureBulkLoadClient is moved to the client package. The lots of changes
are to replace the old endpoint RPC calls with normal client RPC calls to the
RSRpcServices
3. Most of SecureBulkLoad proto is moved into Client proto. The services in
SecureBulkLoad proto are kept for backward compatibility.
4. LoadIncrementalHFiles calls SecureBulkLoadClient always.
5. Bulk load related test cases are all modified to use the new client.
> 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-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)
