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

Sanjay Radia commented on HADOOP-6900:
--------------------------------------

>I do not want to introduce an incompatible change for now.
I don't understand the compatibility argument since this is new API.

We could add a parameter to indicate whether or not continue if a change in the 
sub-tree has occurred. 
I can live with that as long as folks not interpret it to mean that the list 
returned is atomic - if a subdir's content has been 
returned then the iterator will not detect it.
Hairong's patch can go though as Suresh has suggested and we can file another 
one to finalize this API. 




> 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