You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Kai Zheng (JIRA)" <ji...@apache.org> on 2015/06/04 05:47:38 UTC
[jira] [Commented] (HADOOP-12060) Address some issues related to
ByteBuffer type input/output buffers for raw erasure coders
[ https://issues.apache.org/jira/browse/HADOOP-12060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14572060#comment-14572060 ]
Kai Zheng commented on HADOOP-12060:
------------------------------------
I guess there won't be problem for sliced direct ByteBuffers since it's essentially not different from non-sliced ones. Sliced on-heap buffers behave differently regarding {{array}} because it has to maintain {{arrayOffset}} in addition to {{position}}. Would check and ensure this in native codes.
> Address some issues related to ByteBuffer type input/output buffers for raw erasure coders
> ------------------------------------------------------------------------------------------
>
> Key: HADOOP-12060
> URL: https://issues.apache.org/jira/browse/HADOOP-12060
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: io
> Reporter: Kai Zheng
> Assignee: Kai Zheng
>
> In HDFS-8319 [~jingzhao] raised some issues about ByteBuffer type input/output buffers for raw erasure coders:
> * Should support ByteBuffers originated from {{ByteBuffer#slice}} calls;
> * Should clearly spec in Javadoc that no mixing of on-heap buffers and direct buffers are allowed, and with necessary checking codes ensuring the same type of buffers are used.
> In HDFS-8319 patch by [~jingzhao] there are some good refactoring codes that would be incorporated here.
> As discussed open this to address the issues separately.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)