You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Lars Hofhansl (Updated) (JIRA)" <ji...@apache.org> on 2012/01/14 05:56:39 UTC

[jira] [Updated] (HBASE-3584) Allow atomic put/delete in one call

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

Lars Hofhansl updated HBASE-3584:
---------------------------------

     Description: 
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 MVCC it cannot be included in an atomic operation.
So this for Put and Delete only.


  was:
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.

      Issue Type: New Feature  (was: Bug)
         Summary: Allow atomic put/delete in one call  (was: We need to atomically put/delete/increment in one call)
    Hadoop Flags: Reviewed

Changed title, amended description.
                
> 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 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