[
https://issues.apache.org/jira/browse/HBASE-19437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16384649#comment-16384649
]
Hudson commented on HBASE-19437:
--------------------------------
Results for branch master, done in 4 hr 0 min and counting
[build #248 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/248/]:
----
details (if available):
(x) *{color:red}-1 overall{color}*
Committer, please check your recent inclusion of a patch for this issue.
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> 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)
