[
https://issues.apache.org/jira/browse/HDFS-8957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829023#comment-15829023
]
Hadoop QA commented on HDFS-8957:
---------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 5s{color}
| {color:red} HDFS-8957 does not apply to trunk. Rebase required? Wrong Branch?
See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HDFS-8957 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12823394/HDFS-8957.v4.patch |
| Console output |
https://builds.apache.org/job/PreCommit-HDFS-Build/18204/console |
| Powered by | Apache Yetus 0.5.0-SNAPSHOT http://yetus.apache.org |
This message was automatically generated.
> Consolidate client striping input stream codes for stateful read and
> positional read
> ------------------------------------------------------------------------------------
>
> Key: HDFS-8957
> URL: https://issues.apache.org/jira/browse/HDFS-8957
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: erasure-coding
> Affects Versions: 3.0.0-alpha2
> Reporter: Kai Zheng
> Assignee: SammiChen
> Attachments: HDFS-8957-v1.patch, HDFS-8957.v2.patch,
> HDFS-8957.v3.patch, HDFS-8957.v4.patch
>
>
> Currently we have different implementations for client striping read, having
> both *StatefulStripeReader* and *PositionStripeReader*. I attempted to
> consolidate the two implementations into one, and it results in much simpler
> codes, and also better performance. Now in both read paths, it will:
> * Use pooled ByteBuffers, as currently stateful read does;
> * Read directly into application's buffer, as currently positional read does;
> * Try to align and merge multiple stripes, as currently positional read does;
> * Use *ECChunk* version decode API.
> The resultant *StripeReader* is approaching very near now to the ideal state
> desired by next step, employing *ErasureCoder* API instead of
> *RawErasureCoder* API.
> Will upload an initial patch to illustrate the rough change, even though it
> depends on other issues.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]