[
https://issues.apache.org/jira/browse/HBASE-19437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16383930#comment-16383930
]
Hudson commented on HBASE-19437:
--------------------------------
FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #4677 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/4677/])
HBASE-19437 Batch operation can't handle the null result for (chia7712: rev
db131be39a2e4821751be1d654dbaff81024d0ee)
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RSRpcServices.java
* (add)
hbase-server/src/test/java/org/apache/hadoop/hbase/coprocessor/TestIncrementAndAppendWithNullResult.java
> 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,
> HBASE-19437.v1.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)
