You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Bob Hansen (JIRA)" <ji...@apache.org> on 2015/09/25 14:07:04 UTC
[jira] [Commented] (HDFS-9144) Refactor libhdfs into
stateful/ephemeral objects
[ https://issues.apache.org/jira/browse/HDFS-9144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14907970#comment-14907970 ]
Bob Hansen commented on HDFS-9144:
----------------------------------
For clarification, these are all asynchronous (or at least primarily asychronous) interfaces, perhaps with a Future-like blocking mechanism
> Refactor libhdfs into stateful/ephemeral objects
> ------------------------------------------------
>
> Key: HDFS-9144
> URL: https://issues.apache.org/jira/browse/HDFS-9144
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: hdfs-client
> Affects Versions: HDFS-8707
> Reporter: Bob Hansen
>
> In discussion for other efforts, we decided that we should separate several concerns:
> * A posix-like FileSystem/FileHandle object (stream-based, positional reads)
> * An ephemeral ReadOperation object that holds the state for reads-in-progress, which consumes
> * An immutable FileInfo object which holds the block map and file size (and other metadata about the file that we assume will not change over the life of the file)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)