[
https://issues.apache.org/jira/browse/HADOOP-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raghu Angadi updated HADOOP-3121:
---------------------------------
Attachment: HADOOP-3121.patch
I hope attached patch clarifies what I mean. It behaves same as before and does
not add extra line of output that is unecessary.
For e.g. compare 'bin/hadoop fs -ls /other' :
- with the patch attached (*and* trunk) : {noformat}
ls: could not get get listing for '/other' :
org.apache.hadoop.security.AccessControlException: Permission denied: [...]
{noformat}
- with your patch : {noformat}
ls: could not get get listing for '/other' :
org.apache.hadoop.security.AccessControlException: Permission denied: [...]
ls: There were totaly 1 exception(s).
{noformat}
I don't think most command print extra lines like 'ls: There were totaly 1
exception(s)' at the end..'
> dfs -lsr fail with "Could not get listing "
> -------------------------------------------
>
> Key: HADOOP-3121
> URL: https://issues.apache.org/jira/browse/HADOOP-3121
> Project: Hadoop Core
> Issue Type: Bug
> Components: fs
> Affects Versions: 0.16.1
> Reporter: Koji Noguchi
> Assignee: Tsz Wo (Nicholas), SZE
> Priority: Minor
> Fix For: 0.18.3
>
> Attachments: 3121_20081105.patch, 3121_20081106.patch,
> 3121_20081106b.patch, HADOOP-3121.patch
>
>
> (This happened a lot when namenode was extremely slow due to some other
> reasons.)
> % hadoop dfs -lsr /
> failed with
> > Could not get listing for /aaa/bbb/randomfile
> It's probably because file was deleted between items = fs.listStatus( and
> ls(items[i]
> I think lsr should ignore this case and continue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
