Chia-Ping Tsai commented on HBASE-19437:

bq. This seems good to me for branch-2 (after beta-2 RC is cut
Pardon me, I overlooked this comment when committing.

> 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

Reply via email to