[jira] [Commented] (HBASE-9332) OrderedBytes does not decode Strings correctly
[ https://issues.apache.org/jira/browse/HBASE-9332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750897#comment-13750897 ] Hudson commented on HBASE-9332: --- SUCCESS: Integrated in HBase-TRUNK #4436 (See [https://builds.apache.org/job/HBase-TRUNK/4436/]) 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
[jira] [Commented] (HBASE-9332) OrderedBytes does not decode Strings correctly
[ 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
[jira] [Commented] (HBASE-9332) OrderedBytes does not decode Strings correctly
[ https://issues.apache.org/jira/browse/HBASE-9332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750644#comment-13750644 ] Hudson commented on HBASE-9332: --- SUCCESS: Integrated in hbase-0.95 #494 (See [https://builds.apache.org/job/hbase-0.95/494/]) HBASE-9332 OrderedBytes does not decode Strings correctly (stack: rev 1517656) * /hbase/branches/0.95/hbase-common/src/main/java/org/apache/hadoop/hbase/util/OrderedBytes.java * /hbase/branches/0.95/hbase-common/src/main/java/org/apache/hadoop/hbase/util/SimplePositionedByteRange.java * /hbase/branches/0.95/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
[jira] [Commented] (HBASE-9332) OrderedBytes does not decode Strings correctly
[ https://issues.apache.org/jira/browse/HBASE-9332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750530#comment-13750530 ] Hudson commented on HBASE-9332: --- FAILURE: Integrated in hbase-0.95-on-hadoop2 #273 (See [https://builds.apache.org/job/hbase-0.95-on-hadoop2/273/]) HBASE-9332 OrderedBytes does not decode Strings correctly (stack: rev 1517656) * /hbase/branches/0.95/hbase-common/src/main/java/org/apache/hadoop/hbase/util/OrderedBytes.java * /hbase/branches/0.95/hbase-common/src/main/java/org/apache/hadoop/hbase/util/SimplePositionedByteRange.java * /hbase/branches/0.95/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
[jira] [Commented] (HBASE-9332) OrderedBytes does not decode Strings correctly
[
https://issues.apache.org/jira/browse/HBASE-9332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750422#comment-13750422
]
Hadoop QA commented on HBASE-9332:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12599976/0001-HBASE-9332-OrderedBytes-error-decoding-strings.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 4 new
or modified tests.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:red}-1 release audit{color}. The applied patch generated 2 release
audit warnings (more than the trunk's current 0 warnings).
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.TestFullLogReconstruction
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/6899//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6899//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6899//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6899//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6899//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6899//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6899//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6899//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6899//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6899//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/6899//console
This message is automatically generated.
> 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
[jira] [Commented] (HBASE-9332) OrderedBytes does not decode Strings correctly
[ https://issues.apache.org/jira/browse/HBASE-9332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750335#comment-13750335 ] stack commented on HBASE-9332: -- +1 Skimmed. Looks fine. > 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
[jira] [Commented] (HBASE-9332) OrderedBytes does not decode Strings correctly
[ https://issues.apache.org/jira/browse/HBASE-9332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750320#comment-13750320 ] Nicolas Liochon commented on HBASE-9332: I'm +1, if there is no objection I will commit soon (within 1 hour) to get it into the next 0.95 release. > 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
[jira] [Commented] (HBASE-9332) OrderedBytes does not decode Strings correctly
[ https://issues.apache.org/jira/browse/HBASE-9332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750301#comment-13750301 ] Nick Dimiduk commented on HBASE-9332: - Release audit issues are fixed by HBASE-9336. > 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
[jira] [Commented] (HBASE-9332) OrderedBytes does not decode Strings correctly
[
https://issues.apache.org/jira/browse/HBASE-9332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750282#comment-13750282
]
Hadoop QA commented on HBASE-9332:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12599967/0001-HBASE-9332-OrderedBytes-error-decoding-strings.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 4 new
or modified tests.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 findbugs{color}. The patch appears to introduce 1 new
Findbugs (version 1.3.9) warnings.
{color:red}-1 release audit{color}. The applied patch generated 2 release
audit warnings (more than the trunk's current 0 warnings).
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/6897//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6897//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6897//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6897//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6897//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6897//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6897//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6897//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6897//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6897//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/6897//console
This message is automatically generated.
> 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
[jira] [Commented] (HBASE-9332) OrderedBytes does not decode Strings correctly
[
https://issues.apache.org/jira/browse/HBASE-9332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13749580#comment-13749580
]
Hadoop QA commented on HBASE-9332:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12599739/0001-HBASE-9332-OrderedBytes-error-decoding-strings.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 4 new
or modified tests.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 findbugs{color}. The patch appears to introduce 1 new
Findbugs (version 1.3.9) warnings.
{color:red}-1 release audit{color}. The applied patch generated 2 release
audit warnings (more than the trunk's current 0 warnings).
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/6870//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6870//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6870//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6870//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6870//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6870//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6870//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6870//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6870//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6870//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/6870//console
This message is automatically generated.
> 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
>
>
> 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
[jira] [Commented] (HBASE-9332) OrderedBytes does not decode Strings correctly
[ https://issues.apache.org/jira/browse/HBASE-9332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13749433#comment-13749433 ] Ted Yu commented on HBASE-9332: --- +1 > 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 > > > 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
