[
https://issues.apache.org/jira/browse/HBASE-6712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652603#comment-13652603
]
Raymond Liu commented on HBASE-6712:
------------------------------------
[~ted_yu]No, I don't, though it could easily figure one out. Originally, my
point above is that if follow checkAndPut/Delete's style that only allow check
and increment on the same column, we don't need to worry about idempotent issue
as checkAndPut since we checking for equal.
But now , I realized that, even so, we still need to treat it as Increment as
HBASE-3787 is try to handle, since one checkAndIncrement might succeed to +1,
then another succeed to -1, after that a retry of first +1 operation will pass
the check and +1 again, which is not correct and non idempotent.
> Implement checkAndIncrement
> ---------------------------
>
> Key: HBASE-6712
> URL: https://issues.apache.org/jira/browse/HBASE-6712
> Project: HBase
> Issue Type: New Feature
> Components: Client
> Affects Versions: 0.92.1
> Reporter: Stefan Baritchii
> Assignee: Ted Yu
>
> increment should throw an exception if a row does not exist. instead it
> creates the row. checkAndIncrement may be also a solution to it but needs
> development.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
