You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Hive QA (JIRA)" <ji...@apache.org> on 2017/06/28 00:43:00 UTC

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

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

Hive QA commented on HIVE-16960:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12874709/HIVE16960.1.patch

{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 11 failed/errored test(s), 10851 tests executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[tez_smb_main] (batchId=150)
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[dyn_part_max] (batchId=88)
org.apache.hadoop.hive.cli.TestPerfCliDriver.testCliDriver[query14] (batchId=234)
org.apache.hadoop.hive.cli.TestPerfCliDriver.testCliDriver[query16] (batchId=234)
org.apache.hadoop.hive.cli.TestPerfCliDriver.testCliDriver[query94] (batchId=234)
org.apache.hadoop.hive.ql.parse.TestReplicationScenariosAcrossInstances.testBootstrapFunctionReplication (batchId=217)
org.apache.hadoop.hive.ql.parse.TestReplicationScenariosAcrossInstances.testCreateFunctionIncrementalReplication (batchId=217)
org.apache.hadoop.hive.ql.parse.TestReplicationScenariosAcrossInstances.testCreateFunctionWithFunctionBinaryJarsOnHDFS (batchId=217)
org.apache.hive.hcatalog.api.TestHCatClient.testPartitionRegistrationWithCustomSchema (batchId=178)
org.apache.hive.hcatalog.api.TestHCatClient.testPartitionSpecRegistrationWithCustomSchema (batchId=178)
org.apache.hive.hcatalog.api.TestHCatClient.testTableSchemaPropagation (batchId=178)
{noformat}

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

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 11 tests failed
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12874709 - PreCommit-HIVE-Build

> 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
>
>         Attachments: HIVE16960.1.patch
>
>
> 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)