hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arup Malakar (JIRA)" <>
Subject [jira] [Updated] (HIVE-4911) Enable QOP configuration for Hive Server 2 thrift transport
Date Wed, 24 Jul 2013 16:51:48 GMT


Arup Malakar updated HIVE-4911:

    Attachment: HIVE-4911-trunk-1.patch

[~brocknoland]The reason I implemented fromString() instead of using the valueOf() is because
I wanted to use the strings auth, auth-int, auth-conf in the configuration file "hive-site.xml".
As using
this strings for QoP is well understood and can be seen in various online documentations:
But I also wanted to follow enum naming conventions and use enum names AUTH, AUTH_INT and
AUTH_CONF. Given these two are different I couldn't use valueOf() and ended up implementing
fromString() method.

[~thejas] Thanks for quickly reviewing it. I have incorporated all the comments except one.
I need to test the hadoop-at-higher-security-level warning log message part though. Will give
it a try when I get the chance.

I think it may be a good idea to expose another setting for MS as well rather than piggybacking
on That would give finer control on the deployment. The recent changes
are geared towards making it easier. But as Thejas has mentioned, that change could be discussed
in a separate JIRA.
> Enable QOP configuration for Hive Server 2 thrift transport
> -----------------------------------------------------------
>                 Key: HIVE-4911
>                 URL:
>             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 "". 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:

View raw message