[ 
https://issues.apache.org/jira/browse/HIVE-23212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17084903#comment-17084903
 ] 

Hive QA commented on HIVE-23212:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/13000089/HIVE-23212.1.patch

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:green}SUCCESS:{color} +1 due to 17128 tests passed

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/21696/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/21696/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-21696/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}

This message is automatically generated.

ATTACHMENT ID: 13000089 - PreCommit-HIVE-Build

> SemanticAnalyzer::getStagingDirectoryPathname should check for encryption 
> zone only when needed
> -----------------------------------------------------------------------------------------------
>
>                 Key: HIVE-23212
>                 URL: https://issues.apache.org/jira/browse/HIVE-23212
>             Project: Hive
>          Issue Type: Improvement
>          Components: HiveServer2
>            Reporter: Rajesh Balamohan
>            Assignee: Rajesh Balamohan
>            Priority: Minor
>         Attachments: HIVE-23212.1.patch
>
>
> [https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzer.java#L2572]
>  
> When cluster does not have encryption zones configured, this ends up making 2 
> calls to NN unnecessarily. It would be good to guard it with config or check 
> for the KMS config from HDFS and invoke it on need basis.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to