[jira] [Updated] (HIVE-16960) Hive throws an ugly error exception when HDFS sticky bit is set

["Janaki Lahorani (JIRA)" <ji...@apache.org>]

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

Janaki Lahorani updated HIVE-16960:
-----------------------------------
               Labels: newbie  (was: )
        Fix Version/s: 3.0.0
    Affects Version/s: 3.0.0
     Target Version/s: 3.0.0
               Status: Patch Available  (was: Open)

Error from DFS results in ugly stack at the client.  The fix returns hive errors for AccessControlException, *QuotaExceededException, UnresolvedPathException, FileNotFoundException and Invalid File Formats.  First line from the DFS error message is included in the error returned to the client.  SQL State values are defined with these error message and propagated to client.  Internal error 29999 is introduced to handle any error that would require complete stack thrown to the client.

> Hive throws an ugly error exception when HDFS sticky bit is set
> ---------------------------------------------------------------
>
>                 Key: HIVE-16960
>                 URL: https://issues.apache.org/jira/browse/HIVE-16960
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 3.0.0
>            Reporter: Janaki Lahorani
>            Assignee: Janaki Lahorani
>            Priority: Critical
>              Labels: newbie
>             Fix For: 3.0.0
>
>
> When calling LOAD DATA INPATH ... OVERWRITE INTO TABLE ... from a Hive user other than the HDFS file owner, and the HDFS sticky bit is set, then Hive will throw an error exception message that the file cannot be moved due to permission issues.
> Caused by: org.apache.hadoop.security.AccessControlException: Permission denied by sticky bit setting: user=hive, inode=sasdata-2016-04-20-17-13-43-630-e-00001.dlv.bk
> The permission denied is expected, but the error message does not make sense to users + the stack trace displayed is huge. We should display a better error message to users, and maybe provide with help information about how to fix it.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)