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

Jakob Homan commented on HDFS-538:
----------------------------------

bq. How do we distinguish between an empty directory and a non-existent file 
(or directory)?
The similar method {{getFileStatus()}} returns a FileNotFoundException, which 
seems the most reasonable and expected behavior.

The API documentation is exceedingly poor for this method: what happens if the 
passed-in path is not a directory?

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

Reply via email to