[
https://issues.apache.org/jira/browse/HBASE-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13182327#comment-13182327
]
Lars Hofhansl commented on HBASE-3584:
--------------------------------------
Should we do this before "client 2.0"?
What should the client side API look like?
Something like: AtomicRowOperation (which implements Row, so can itself be
batched), which wraps a set Put/Delete/Increment/Append (all for the same
rowkey)?
Compared to a straight put(List<Put>), this would probably be slower as we
cannot do the same mini batching (not with a *lot* of refactoring).
Also it is not entirely clear that this could even work with Increment/Append
of the special immediate-visibility that those need. So maybe start with
Put/Delete.
> We need to atomically put/delete/increment in one call
> ------------------------------------------------------
>
> Key: HBASE-3584
> URL: https://issues.apache.org/jira/browse/HBASE-3584
> Project: HBase
> Issue Type: Bug
> Reporter: ryan rawson
>
> Right now we have the following calls:
> put(Put)
> delete(Delete)
> increment(Increments)
> But we cannot combine all of the above in a single call, complete with a
> single row lock. It would be nice to do that.
> It would also allow us to do a CAS where we could do a put/increment if the
> check succeeded.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
