[ https://issues.apache.org/jira/browse/HBASE-19437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chia-Ping Tsai updated HBASE-19437: ----------------------------------- Release Note: The result from server is changed from null to Result.EMPTY_RESULT when Append/Increment operation can't retrieve any data from server, (was: If Mutation#isReturnResults is false and RegionObserver#preAppendAfterRowLock doesn't return null, the result from server is changed from null to Result.EMPTY_RESULT) > Batch operation can't handle the null result for Append/Increment > ----------------------------------------------------------------- > > Key: HBASE-19437 > URL: https://issues.apache.org/jira/browse/HBASE-19437 > Project: HBase > Issue Type: Bug > Components: Usability > Reporter: Chia-Ping Tsai > Assignee: Chia-Ping Tsai > Priority: Critical > Fix For: 2.0.0 > > Attachments: HBASE-19437.v0.patch, HBASE-19437.v0.patch > > > But the Table#append and #increment can handle the null result...that is an > inconsistent behavior for user. > I have noticed two scenarios that server will return null result to user. > # postAppend/postIncrement return null > # mutation.isReturnResults() is false and > preIncrementAfterRowLock/preAppendAfterRowLock doesn't return null > We should wrap the null to empty result on server side. CP user should throw > Exception rather than return null if they intend to say something is broken. -- This message was sent by Atlassian JIRA (v7.6.3#76005)