hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hairong Kuang (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6900) FileSystem#listLocatedStatus should not throw generic RuntimeException to indicate error conditions
Date Wed, 11 Aug 2010 00:27:18 GMT

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

Hairong Kuang commented on HADOOP-6900:
---------------------------------------

> I don't understand the compatibility argument since this is new API.

Even though this is a new API, but mapreduce already has some logic in their code traversing
the input directories and getting file status/block locations. Existing code does not allow
any concurrent modification to input directories.

I agree that allowing concurrent modification could be an option, but lets do it in a different
jira.

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


Mime
View raw message