You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2012/08/13 09:25:38 UTC
[jira] [Commented] (HBASE-6565) hbase coprocessor return the
Map object sometimes have a wrong size
[ https://issues.apache.org/jira/browse/HBASE-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13432970#comment-13432970 ]
Hadoop QA commented on HBASE-6565:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12540615/Coprocessor-result-thread%20unsafe-bug-fix.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
-1 patch. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/2554//console
This message is automatically generated.
> hbase coprocessor return the Map<byte[],R> object sometimes have a wrong size
> -----------------------------------------------------------------------------
>
> Key: HBASE-6565
> URL: https://issues.apache.org/jira/browse/HBASE-6565
> Project: HBase
> Issue Type: Bug
> Components: client
> Affects Versions: 0.94.0
> Environment: hadoop1.0.2,hbase0.94,jdk1.6
> Reporter: Yuan Kang
> Labels: patch
> Attachments: Coprocessor-result-thread unsafe-bug-fix.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> I develop a coprocessor program ,but found some different results in repeated tests.for example,normally,the result's size is 10.but sometimes it appears 9.
> I read the HTable.java code,found a TreeMap(thread-unsafe) be used in multithreading environment.It cause the bug happened
--
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