hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jakob Homan (Commented) (JIRA)" <>
Subject [jira] [Commented] (HIVE-2643) Recent patch prevents Hadoop confs from loading in 0.20.204
Date Mon, 12 Dec 2011 20:07:32 GMT


Jakob Homan commented on HIVE-2643:

I've applied HIVE-2643.1.patch.txt (the only ASF-licensed patch; are the others artifacts
of the issue name confusion?) to the RC3 tag in svn, built a new package and run against our
204 cluster and everything is working now.  Didn't do a code review, but +1 on the result.
> Recent patch prevents Hadoop confs from loading in 0.20.204
> -----------------------------------------------------------
>                 Key: HIVE-2643
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Configuration
>            Reporter: Jakob Homan
>            Assignee: Carl Steinbach
>            Priority: Blocker
>         Attachments: HIVE-2643.1.patch.txt, HIVE-2643.D747.1.patch, HIVE-2643.D753.1.patch,
HIVE-2643.D759.1.patch, HIVE-2643.D759.2.patch, HIVE-2643.D765.1.patch
> After the application of HIVE-2362, we're unable to run queries against the Hive cluster
(RC2 and 3):
> {noformat} Failed to set permissions of path: /user/jhoman-667872320/.staging
to 0700
>         at org.apache.hadoop.fs.FileUtil.checkReturnValue(
>         at org.apache.hadoop.fs.FileUtil.setPermission(
>         at org.apache.hadoop.fs.RawLocalFileSystem.setPermission(
>         at org.apache.hadoop.fs.RawLocalFileSystem.mkdirs(
>         at org.apache.hadoop.fs.FilterFileSystem.mkdirs(
>         at org.apache.hadoop.mapreduce.JobSubmissionFiles.getStagingDir({noformat}
> this is due to all the hadoop confs not being loaded and the LocalJobRunner (which builds
staging directories in this manner) being used instead of the regular one. It's also not possible
to access the hdfs since no default fs is specified.  
> Reverting 2362 fixes this, but I've not yet looked at that patch to see the exact cause.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message