[
https://issues.apache.org/jira/browse/HIVE-4911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arup Malakar updated HIVE-4911:
-------------------------------
Attachment: HIVE-4911-trunk-2.patch
New changes:
1. Incorporated sasl.qop renaming of param
2. Moved getHadoopSaslProperties to HadoopThriftAuthBridge
I can't get it to compile it with the following arguments though. The classes I
made change to compile fine but the SessionState.java complains:
{code}
compile:
[echo] Project: ql
[javac] Compiling 898 source files to
/Users/malakar/code/oss/hive/build/ql/classes
[javac]
/Users/malakar/code/oss/hive/ql/src/java/org/apache/hadoop/hive/ql/session/SessionState.java:35:
package org.apache.commons.io does not exist
[javac] import org.apache.commons.io.FileUtils;
[javac] ^
[javac]
/Users/malakar/code/oss/hive/ql/src/java/org/apache/hadoop/hive/ql/session/SessionState.java:743:
cannot find symbol
[javac] symbol : variable FileUtils
[javac] location: class org.apache.hadoop.hive.ql.session.SessionState
[javac] FileUtils.deleteDirectory(resourceDir);
[javac] ^
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 2 errors
{code}
> 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,
> HIVE-4911-trunk-2.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
