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

Haohui Mai commented on HDFS-9144:
----------------------------------

bq. Stateful quasi-posix API that will be familiar and easy to consume

Can you elaborate what do you mean by familiar and easy to consume? Are you 
talking about the filesystem API in C++1y 
(https://msdn.microsoft.com/en-us/library/hh874694.aspx)?

There's no reference of RPCEngine in DataNodeConnection.

I think the plan might be too grand to execute. It needs to be broken down. 
Maybe it's nice to start with implementing AsyncReadBlockOperation and its 
cancel() method?




> 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
>            Assignee: 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)

Reply via email to