hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chia-Ping Tsai (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-19437) Batch operation can't handle the null result for Append/Increment
Date Wed, 06 Dec 2017 03:16:01 GMT

     [ https://issues.apache.org/jira/browse/HBASE-19437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chia-Ping Tsai updated HBASE-19437:
-----------------------------------
    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.



  was:
The null from postAppend/postIncrement sparks inconsistent behavior. The Table#append and
#increment can handle the null result but the batch operation throws IllegalStateException.

We should wrap the null from postAppend/postIncrement to empty result since cp user should
throw IOException rather than return null if they intend to say something is broken.




> 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
>            Reporter: Chia-Ping Tsai
>            Assignee: Chia-Ping Tsai
>             Fix For: 2.0.0
>
>
> 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
(v6.4.14#64029)

Mime
View raw message