Details
Critical Description
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.