[
https://issues.apache.org/jira/browse/HDFS-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798869#action_12798869
]
Hairong Kuang commented on HDFS-878:
------------------------------------
> I also like the proposal of having a DFSFileStatus
This still adds cost to the list directory operation and needs to be cautious.
Zheng and Dhruba, you have not answered my question why it is not good enough
that DFSOutputSream provides the visible length and "under construction"
information. Do you have a use case that you have to get those information from
getFileStatus operation?
> FileStatus should have a field "isUnderConstruction"
> ----------------------------------------------------
>
> Key: HDFS-878
> URL: https://issues.apache.org/jira/browse/HDFS-878
> Project: Hadoop HDFS
> Issue Type: New Feature
> Reporter: Zheng Shao
> Assignee: Zheng Shao
>
> Currently DFSClient has no way to know whether a file is under construction
> or not, unless we open the file and get locatedBlocks (which is much more
> costly).
> However, the namenode knows whether each INode is under construction or not.
> We should expose that information from NameNode.getListing(), to
> DFSClient.listPaths(), to DistributedFileSystem.listStatus().
> We should also expose that information through DFSInputStream and
> DFSDataInputStream if not there yet.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
