[
https://issues.apache.org/jira/browse/HDFS-8319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14571918#comment-14571918
]
Kai Zheng commented on HDFS-8319:
---------------------------------
bq. there is no API level restriction to prevent the mixing util we hit
exception during the decoding. I would prefer the API to be more clear and
friendly. And before we have this improvement, I think we need the direct
buffer detection change to avoid exception in mixing scenarios.
Good suggestions! How about: 1) add clear Javadoc in the APIs? 2) add codes to
check the requirement, like {{ensureTheSameBuffer}} similar to
{{ensureLength}}? I did ever consider to spec the input/output buffers, but
forgot at all later.
bq. This lead to wrong decoding result in my test.
So looks like the {{inputOffsets}} doesn't work? Do you have or need the fix
for this issue? If not, let me fix this separately, adding tests for it.
> Erasure Coding: support decoding for stateful read
> --------------------------------------------------
>
> Key: HDFS-8319
> URL: https://issues.apache.org/jira/browse/HDFS-8319
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Jing Zhao
> Assignee: Jing Zhao
> Attachments: HDFS-8319.001.patch, HDFS-8319.002.patch,
> HDFS-8319.003.patch
>
>
> HDFS-7678 adds the decoding functionality for pread. This jira plans to add
> decoding to stateful read.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
