[
https://issues.apache.org/jira/browse/HDFS-8901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15464013#comment-15464013
]
Kai Zheng commented on HDFS-8901:
---------------------------------
Hi [~Sammi] & [~zhz],
Thanks for the discussion. Sorry for the late. I have other thought about
adding the new {{readAll}} API to {{BlockReader}}.
bq. Thanks for adding the ByteBuffer version of readAll. Due to the size of the
current patch, can we create a separate JIRA just to add this API? It will go
through quickly and we can focus on the main logic on this JIRA.
Looking at HDFS-10839 that does this work, it looks like to be more natural to
add the API as {{readFully(ByteBuffer buf)}} in {{ByteBufferReadable}}
interface. However that would involve a large change and may take some time to
happen. Could we leave this work as follow-on to improve and move on this
without doing that?
> Use ByteBuffer in striping positional read
> ------------------------------------------
>
> Key: HDFS-8901
> URL: https://issues.apache.org/jira/browse/HDFS-8901
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Kai Zheng
> Assignee: SammiChen
> Attachments: HDFS-8901-v10.patch, HDFS-8901-v17.patch,
> HDFS-8901-v18.patch, HDFS-8901-v19.patch, HDFS-8901-v2.patch,
> HDFS-8901-v3.patch, HDFS-8901-v4.patch, HDFS-8901-v5.patch,
> HDFS-8901-v6.patch, HDFS-8901-v7.patch, HDFS-8901-v8.patch,
> HDFS-8901-v9.patch, HDFS-8901.v11.patch, HDFS-8901.v12.patch,
> HDFS-8901.v13.patch, HDFS-8901.v14.patch, HDFS-8901.v15.patch,
> HDFS-8901.v16.patch, initial-poc.patch
>
>
> Native erasure coder prefers to direct ByteBuffer for performance
> consideration. To prepare for it, this change uses ByteBuffer through the
> codes in implementing striping position read. It will also fix avoiding
> unnecessary data copying between striping read chunk buffers and decode input
> buffers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
