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

Phabricator updated HIVE-2643:
------------------------------

    Attachment: HIVE-2643.D765.1.patch

cwsteinbach requested code review of "HIVE-2643 [jira] Recent patch prevents 
Hadoop confs from loading in 0.20.204".
Reviewers: JIRA

  HIVE-2643

  After the application of <a 
href="https://issues.apache.org/jira/browse/HIVE-2362"; title="HiveConf 
properties not appearing in the output of 'set' or 'set 
-v'"><del>HIVE-2362</del></a>, we're unable to run queries against the Hive 
cluster (RC2 and 3):  <div class="preformatted panel" style="border-width: 
1px;"><div class="preformattedContent panelContent"> <pre>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)</pre>
 </div>
 </div>

  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.

TEST PLAN
  EMPTY

REVISION DETAIL
  https://reviews.facebook.net/D765

AFFECTED FILES
  common/build.xml
  common/src/java/org/apache/hadoop/hive/conf/HiveConf.java
  common/src/test/org/apache/hadoop/hive/conf/TestHiveConf.java
  common/src/test/resources/core-site.xml
  common/src/test/resources/hive-site.xml
  ql/src/java/org/apache/hadoop/hive/ql/exec/FetchOperator.java

MANAGE HERALD DIFFERENTIAL RULES
  https://reviews.facebook.net/herald/view/differential/

WHY DID I GET THIS EMAIL?
  https://reviews.facebook.net/herald/transcript/1617/

Tip: use the X-Herald-Rules header to filter Herald messages in your client.

                
> 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

        

Reply via email to