You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "John Sichi (Commented) (JIRA)" <ji...@apache.org> on 2011/12/12 20:35:30 UTC
[jira] [Commented] (HIVE-2643) Recent patch prevents Hadoop confs
from loading in 0.20.204
[ https://issues.apache.org/jira/browse/HIVE-2643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13167701#comment-13167701 ]
John Sichi commented on HIVE-2643:
----------------------------------
Marek and I will take a look into the arc confusion with the JIRA reference.
> Recent patch prevents Hadoop confs from loading in 0.20.204
> -----------------------------------------------------------
>
> Key: HIVE-2643
> URL: https://issues.apache.org/jira/browse/HIVE-2643
> 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}java.io.IOException: Failed to set permissions of path: /user/jhoman-667872320/.staging to 0700
> at org.apache.hadoop.fs.FileUtil.checkReturnValue(FileUtil.java:680)
> at org.apache.hadoop.fs.FileUtil.setPermission(FileUtil.java:653)
> at org.apache.hadoop.fs.RawLocalFileSystem.setPermission(RawLocalFileSystem.java:483)
> at org.apache.hadoop.fs.RawLocalFileSystem.mkdirs(RawLocalFileSystem.java:318)
> at org.apache.hadoop.fs.FilterFileSystem.mkdirs(FilterFileSystem.java:183)
> at org.apache.hadoop.mapreduce.JobSubmissionFiles.getStagingDir(JobSubmissionFiles.java:116){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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira