Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <1317651663.161071263241314568.JavaMail.jira@brutus.apache.org>
Date: Mon, 11 Jan 2010 20:21:54 +0000 (UTC)
From: "Zheng Shao (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Subject: [jira] Commented: (HDFS-879) FileStatus should have the visible
 length of the file
In-Reply-To: <1530576059.105131262894574653.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Zheng Shao commented on HDFS-879:
---------------------------------

A mistake in 2A above. FileStatus should be DFSFileStatus.
Also for 2B, talked with Dhruba offline. A better way for this to send the latest length NOT in heartbeat but in a similar manner as the new block creation event.


> FileStatus should have the visible length of the file
> -----------------------------------------------------
>
>                 Key: HDFS-879
>                 URL: https://issues.apache.org/jira/browse/HDFS-879
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Zheng Shao
>            Assignee: Zheng Shao
>
> Currently, {{FileStatus}} returned by {{DistributedFileSystem.listStatus()}} (which goes through {{DFSClient.listPath()}} then {{NameNode.getListing()}}) does not have the latest file length, if the file is still open for write.
> We should make changes in {{DFSClient.listPath()}} to override the length of the file, if the file is under construction.
> This depends on adding a {{isUnderConstruction}} field in {{FileStatus}}.

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