[
https://issues.apache.org/jira/browse/HIVE-4911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718778#comment-13718778
]
Thejas M Nair commented on HIVE-4911:
-------------------------------------
[~amalakar] I have responded to your comment about "auth" param name in jdbc
connection string.
I think the refactoring that you have done to add
MetaStoreUtils.getMetaStoreSaslProperties(conf) is a good idea.
As you pointed out using this SaslRpcServer is likely to give compilation
issues with 0.20. Looks like that will need to go into hadoop shims classes.
Can you ensure that you are able to build with hadoop 0.20 ?
bq. I think it may be a good idea to expose another setting for MS as well
rather than piggybacking on hadoop.rpc.protection. That would give finer
control on the deployment.
I think it is better to not increase complexity by adding more configs, unless
there is really an use case for it.
[~fwiffo] With the new patch QOP for HMS should work with hadoop.rpc.protection
being set. Do you want to try it out ?
> Enable QOP configuration for Hive Server 2 thrift transport
> -----------------------------------------------------------
>
> Key: HIVE-4911
> URL: https://issues.apache.org/jira/browse/HIVE-4911
> Project: Hive
> Issue Type: New Feature
> Reporter: Arup Malakar
> Assignee: Arup Malakar
> Attachments: HIVE-4911-trunk-0.patch, HIVE-4911-trunk-1.patch
>
>
> The QoP for hive server 2 should be configurable to enable encryption. A new
> configuration should be exposed "hive.server2.thrift.rpc.protection". This
> would give greater control configuring hive server 2 service.
--
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
