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

Hadoop QA commented on HADOOP-7943:
-----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  
http://issues.apache.org/jira/secure/attachment/12511524/hadoop-7943-1.0.0v2.patch
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    -1 tests included.  The patch doesn't appear to include any new or modified 
tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    -1 patch.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/524//console

This message is automatically generated.
                
> DFS shell get/copy gives weird errors when permissions are wrong with 
> directories
> ---------------------------------------------------------------------------------
>
>                 Key: HADOOP-7943
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7943
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 0.20.205.0
>            Reporter: Ben West
>            Priority: Minor
>              Labels: hdfs, shell
>         Attachments: hadoop-7943-1.0.0.patch, hadoop-7943-1.0.0v2.patch, 
> hadoop-7943.patch, hadoop-7943.patch
>
>
> Let /foo be a *directory* in HDFS (issue does not occur with files) and /bar 
> be a local dir. Do something like:
> {code}
> $ chmod u-w /bar
> $ hadoop -get /foo/myfile /bar
> copyToLocal: Permission denied  # correctly tells me permission is denied
> $ hadoop -get /foo /bar
> copyToLocal: null           
> $ hadoop -get /foo/ /bar
> copyToLocal: No such file or directory
> {code}
> I've been banging my head for a bit trying to figure out why hadoop thinks my 
> directory doesn't exist, but it turns out the problem was just with my local 
> permissions. The "Permission denied" error would've been a lot nicer to get.

--
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