[
https://issues.apache.org/jira/browse/HDFS-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12793802#action_12793802
]
Arun C Murthy commented on HDFS-814:
------------------------------------
bq. Related thought: should we move DFSDataInputStream outside of DFSClient
since it will have some significant functionality i.e. getVisibleLength?
Let me elaborate: My thinking is that we need an HDFS specific input-stream
which is *the* input-stream with features such as getVisibleLength etc.
(possibly even getCurrentDatanode, getCurrentBlock ?)
> Add an api to get the visible length of a DFSDataInputStream.
> -------------------------------------------------------------
>
> Key: HDFS-814
> URL: https://issues.apache.org/jira/browse/HDFS-814
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: hdfs client
> Reporter: Tsz Wo (Nicholas), SZE
> Assignee: Tsz Wo (Nicholas), SZE
> Fix For: 0.21.0, 0.22.0
>
> Attachments: h814_20091221.patch
>
>
> Hflush guarantees that the bytes written before are visible to the new
> readers. However, there is no way to get the length of the visible bytes.
> The visible length is useful in some applications like SequenceFile.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
