hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jakob Homan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-538) DistributedFileSystem::listStatus incorrectly returns null for empty result sets
Date Fri, 14 Aug 2009 19:02:14 GMT

    [ https://issues.apache.org/jira/browse/HDFS-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12743365#action_12743365

Jakob Homan commented on HDFS-538:

Whoops.  Looks like Konstantin and I were responding at the same time.  As a more general
point, it seems quite preferable for methods not to return null, but either return the object
they promised to or throw an exception.

> DistributedFileSystem::listStatus incorrectly returns null for empty result sets
> --------------------------------------------------------------------------------
>                 Key: HDFS-538
>                 URL: https://issues.apache.org/jira/browse/HDFS-538
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Jakob Homan
>            Assignee: Jakob Homan
> Currently the listStatus method returns null if no files match the request.  This differs
from the Checksum/LocalFileSystem implementation, which returns an empty array, and the nontvery-explict
prescription of the FileSystem interface: "{{@return the statuses of the files/directories
in the given patch}}"  It's better to return an empty collection than have to add extra null
checks.  The method should return an empty array.

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

View raw message