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

Hive QA commented on HIVE-23357:
--------------------------------



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

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

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

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

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: 13001918 - PreCommit-HIVE-Build

> Allow queue user to be configured separately from doAs
> ------------------------------------------------------
>
>                 Key: HIVE-23357
>                 URL: https://issues.apache.org/jira/browse/HIVE-23357
>             Project: Hive
>          Issue Type: Improvement
>          Components: HiveServer2
>    Affects Versions: 4.0.0
>            Reporter: John Sherman
>            Assignee: John Sherman
>            Priority: Major
>         Attachments: HIVE-23357.1.patch
>
>
> There are cases where we may want to submit to a YARN queue as the logged in 
> user but not require full doas for writing of HDFS or authorization.
> A setting could be added to control this behavior:
> set hive.server2.tez.queue.access.method=default
> default is to follow doas setting (the current method)
>  loggedin is to always username of logged in user.



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

Reply via email to