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

Suresh Srinivas commented on HADOOP-6900:
-----------------------------------------

+ 1 for the patch.

bq. Unfortunately not allowing concurrent modification on the input directories 
is the semantics that map/reduce has it now. I do not want to introduce an 
incompatible change for now.

Given that this is a new API, I am not sure handling concurrent modification 
and ignoring deleted directories is a real backward compatibility issue for 
mapreduce. Mapreduce folks can comment about what is more suitable. We can 
address this issue in a separate jira though.

> FileSystem#listLocatedStatus should not throw generic RuntimeException to 
> indicate error conditions
> ---------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-6900
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6900
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Suresh Srinivas
>            Assignee: Hairong Kuang
>         Attachments: listFilesIO.patch, listFilesIO1.patch
>
>
> HDFS-6870 introduced FileSystem#listLocatedStatus(), that returns an Iterator 
> to iterate through LocatedFileStatus for files under a directory or 
> recursively under a sub-directory. Iterator currently throws generic 
> RuntimeException to indicate error conditions. API needs to be changed to 
> throw appropriate exceptions to indicate error conditions.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to