[
https://issues.apache.org/jira/browse/HBASE-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13206357#comment-13206357
]
Kannan Muthukkaruppan commented on HBASE-3584:
----------------------------------------------
Lars: Yes... it would be tricky since we have some app level code already
relying on RowMutation.
Regarding name suggestions, RowMutations sounds good.. since one is likely to
use this only when you typically have a more than one mutation (typically a mix
of deletes and puts). RowChanges or RowOperations would be some alternatives.
How about RowOperations (if we feel RowMutations vs RowMutation is too
similar/confusing).
> Allow atomic put/delete in one call
> -----------------------------------
>
> Key: HBASE-3584
> URL: https://issues.apache.org/jira/browse/HBASE-3584
> Project: HBase
> Issue Type: New Feature
> Components: client, coprocessors, regionserver
> Reporter: ryan rawson
> Assignee: Lars Hofhansl
> Fix For: 0.94.0
>
> Attachments: 3584-final.txt, 3584-v1.txt, 3584-v3.txt
>
>
> 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.
> -----
> Amendment:
> Since Increment does not currently support MVCC it cannot be included in an
> atomic operation.
> So this for Put and Delete only.
--
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
