[
https://issues.apache.org/jira/browse/HBASE-9332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750886#comment-13750886
]
Hudson commented on HBASE-9332:
-------------------------------
FAILURE: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #698 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/698/])
HBASE-9332 OrderedBytes does not decode Strings correctly (stack: rev 1517655)
*
/hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/util/OrderedBytes.java
*
/hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/util/SimplePositionedByteRange.java
*
/hbase/trunk/hbase-common/src/test/java/org/apache/hadoop/hbase/util/TestOrderedBytes.java
> OrderedBytes does not decode Strings correctly
> ----------------------------------------------
>
> Key: HBASE-9332
> URL: https://issues.apache.org/jira/browse/HBASE-9332
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.95.2
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Fix For: 0.98.0, 0.96.0
>
> Attachments:
> 0001-HBASE-9332-OrderedBytes-error-decoding-strings.patch,
> 0001-HBASE-9332-OrderedBytes-error-decoding-strings.patch,
> 0001-HBASE-9332-OrderedBytes-error-decoding-strings.patch
>
>
> While writing a test describing the expected behavior for HBASE-9283, I
> discovered an error in String decoding. The error occurs when the string
> being decoded does not start at position 0. The unit tests were originally
> designed to cover this scenario, but this condition slipped in the transition
> to PositionedByteBuffer.
> Update the tests to cover this scenario and fix the String decoding logic.
> String appears to be the only codec affected. This error is only in decoding
> -- encoding produces correct byte[].
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
