[
https://issues.apache.org/jira/browse/HBASE-13701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15379946#comment-15379946
]
Jerry He commented on HBASE-13701:
----------------------------------
I have tested v4.patch on live cluster with all the combinations I can think of.
1. non-Kerberos and Kerberos
2. old non-secure client and old secure client talking to new server for
backward compatibility.
All works fine.
Do you all have other comments? I can fix the question raised by my last
comment separately.
> 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.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)
