hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-3584) We need to atomically put/delete/increment in one call
Date Thu, 12 Jan 2012 21:51:39 GMT

    [ https://issues.apache.org/jira/browse/HBASE-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13185272#comment-13185272

Lars Hofhansl commented on HBASE-3584:

Thanks Ted. Looked at the coprocessor API more. Unfortunately both pre and post hooks for
Delete and Put take a WALEdit argument; the WALEdit is only created when the Delete/Put happens.
Could move creation of all WALEdits up in this case and pass WALEdits down, seems nasty.

It turns out there are some inconsistencies with Put and Delete right now. The Put posthook
is executed after the region was released, but the Delete posthook is executed with the region
lock held.

Will address your other comments.

> 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
>            Assignee: Lars Hofhansl
>         Attachments: 3584-v1.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.

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


View raw message