[
https://issues.apache.org/jira/browse/HBASE-13701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15340555#comment-15340555
]
Enis Soztutar commented on HBASE-13701:
---------------------------------------
bq. I wondered how that is going to work out for the Compatibility if I do away
the SecureBulkLoadEndpoint but provide the same service on the RSRpcServices.
We can keep SecureBulkLoadEndpoint as a class, which is just a thin wrapper to
call the underlying methods in the regionserver. So that even if you have
configured it, 1.x client will still work agains 2.x clusters.
> 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
>
> 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)
