[ https://issues.apache.org/jira/browse/HBASE-5515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhihong Yu updated HBASE-5515: ------------------------------ Comment: was deleted (was: -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12517282/HBASE-5515.D2067.15.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 2 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. -1 javac. The patch appears to cause mvn compile goal to fail. -1 findbugs. The patch appears to cause Findbugs (version 1.3.9) to fail. +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: Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/1117//testReport/ Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/1117//console This message is automatically generated.) > Add a processRow API that supports atomic multiple reads and writes on a row > ---------------------------------------------------------------------------- > > Key: HBASE-5515 > URL: https://issues.apache.org/jira/browse/HBASE-5515 > Project: HBase > Issue Type: New Feature > Reporter: Scott Chen > Assignee: Scott Chen > Attachments: HBASE-5515.D2067.1.patch, HBASE-5515.D2067.10.patch, > HBASE-5515.D2067.11.patch, HBASE-5515.D2067.12.patch, > HBASE-5515.D2067.13.patch, HBASE-5515.D2067.14.patch, > HBASE-5515.D2067.15.patch, HBASE-5515.D2067.16.patch, > HBASE-5515.D2067.17.patch, HBASE-5515.D2067.2.patch, > HBASE-5515.D2067.3.patch, HBASE-5515.D2067.4.patch, HBASE-5515.D2067.5.patch, > HBASE-5515.D2067.6.patch, HBASE-5515.D2067.7.patch, HBASE-5515.D2067.8.patch, > HBASE-5515.D2067.9.patch > > > We have modified HRegion.java internally to do some atomic row processing. It > will be nice to have a plugable API for this. -- 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