[
https://issues.apache.org/jira/browse/HBASE-5736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248607#comment-13248607
]
Hadoop QA commented on HBASE-5736:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12521707/HBASE-5736.D2649.3.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 6 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hbase.io.hfile.TestForceCacheImportantBlocks
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/1432//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/1432//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/1432//console
This message is automatically generated.
> ThriftServerRunner.HbaseHandler.mutateRow() does not use ByteBuffer correctly
> -----------------------------------------------------------------------------
>
> Key: HBASE-5736
> URL: https://issues.apache.org/jira/browse/HBASE-5736
> Project: HBase
> Issue Type: Bug
> Reporter: Scott Chen
> Assignee: Scott Chen
> Attachments: HBASE-5736.D2649.1.patch, HBASE-5736.D2649.2.patch,
> HBASE-5736.D2649.3.patch
>
>
> We have fixed similar bug in
> https://issues.apache.org/jira/browse/HBASE-5507
> It uses ByteBuffer.array() to read the ByteBuffer.
> This will ignore the offset return the whole underlying byte array.
> The bug can be triggered by using framed Transport thrift servers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
