[
https://issues.apache.org/jira/browse/HIVE-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phabricator updated HIVE-4225:
------------------------------
Attachment: HIVE-4225.D10959.1.patch
fwiffo requested code review of "HIVE-4225 [jira] HiveServer2 does not support
SASL QOP".
Reviewers: JIRA
A trunk patch which honors the QOP setting of hadoop.rpc.protection variable
when a Configuration is used to initialize the client/server connection for
both HiveServer2 and HiveMetastore
HiveServer2 implements Kerberos authentication through SASL framework, but does
not support setting QOP.
TEST PLAN
I installed a patched version of Hive on a Kerberos enabled CDH 4.2.1 cluster
with hadoop.rpc.protection set to both privacy and integrity. I observed the
expected behavior from both HiveServer2 and HiveMetastore when using Hue's
Python Thrift client (patched with HUE-1288).
REVISION DETAIL
https://reviews.facebook.net/D10959
AFFECTED FILES
metastore/src/java/org/apache/hadoop/hive/metastore/HiveMetaStore.java
metastore/src/java/org/apache/hadoop/hive/metastore/HiveMetaStoreClient.java
service/src/java/org/apache/hive/service/auth/HiveAuthFactory.java
shims/src/common-secure/java/org/apache/hadoop/hive/thrift/HadoopThriftAuthBridge20S.java
shims/src/common/java/org/apache/hadoop/hive/thrift/HadoopThriftAuthBridge.java
MANAGE HERALD RULES
https://reviews.facebook.net/herald/view/differential/
WHY DID I GET THIS EMAIL?
https://reviews.facebook.net/herald/transcript/26193/
To: JIRA, fwiffo
> HiveServer2 does not support SASL QOP
> -------------------------------------
>
> Key: HIVE-4225
> URL: https://issues.apache.org/jira/browse/HIVE-4225
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2, Shims
> Affects Versions: 0.11.0
> Reporter: Chris Drome
> Assignee: Chris Drome
> Attachments: HIVE-4225-1.patch, HIVE-4225.D10959.1.patch,
> HIVE-4225.patch
>
>
> HiveServer2 implements Kerberos authentication through SASL framework, but
> does not support setting QOP.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
