[ 
https://issues.apache.org/jira/browse/HIVE-17539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vineet Garg updated HIVE-17539:
-------------------------------
    Fix Version/s:     (was: 3.0.0)
                   3.1.0

Deferring this to 3.1.0 since the branch for 3.0.0 has been cut off. Please 
update the JIRA if you would like to get your patch in 3.0.0.

> User impersonation failure is not propagated by server as a failure to client
> -----------------------------------------------------------------------------
>
>                 Key: HIVE-17539
>                 URL: https://issues.apache.org/jira/browse/HIVE-17539
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2
>    Affects Versions: 3.0.0
>            Reporter: anishek
>            Assignee: anishek
>            Priority: Critical
>             Fix For: 3.1.0
>
>
> As part of HIVE-17512 we fixed the distCp user impersonation if doAs = false 
> and configured "hive.distcp.privileged.doAs" is same as the user running 
> hiveServer. However in the event of not applying the source in patch for 
> HIVE-17512 and running the corresponding test run in HIVE-17512 with older 
> code there is impersonation error in the hive server logs, however the driver 
> returns an "exitValue"  of 0 which is wrong, since the copy failed we should 
> return the error code appropriately.
> also since the table creation happens and only data is missing there is a 
> possibility that the last.repl.id on the table is the latest value with the 
> data missing and coupled with no error returned to the client this can lead 
> to serious replication inconsistencies.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to