[
https://issues.apache.org/jira/browse/HADOOP-13214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15308194#comment-15308194
]
Hadoop QA commented on HADOOP-13214:
------------------------------------
| (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 4s {color}
| {color:red} HADOOP-13214 does not apply to trunk. Rebase required? Wrong
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12807208/HADOOP-13214.2.patch |
| JIRA Issue | HADOOP-13214 |
| Console output |
https://builds.apache.org/job/PreCommit-HADOOP-Build/9627/console |
| Powered by | Apache Yetus 0.4.0-SNAPSHOT http://yetus.apache.org |
This message was automatically generated.
> sync(0); next(); yields wrong key-values on block-compressed files
> ------------------------------------------------------------------
>
> Key: HADOOP-13214
> URL: https://issues.apache.org/jira/browse/HADOOP-13214
> Project: Hadoop Common
> Issue Type: Bug
> Components: io
> Reporter: Illes S
> Labels: easyfix, newbie, patch
> Attachments: HADOOP-13214.2.patch, HADOOP-13214.patch
>
>
> Calling {{sync(0); next(...);}} on a block-compressed {{SequenceFile.Reader}}
> that has already been used may not yield the key-values at the beginning, but
> those following the previous position. The issue is caused by {{sync(0)}} not
> releasing previously buffered keys and values. The issue was introduced by
> HADOOP-6196.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
