You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2009/04/28 18:51:31 UTC

[jira] Updated: (HBASE-493) Write-If-Not-Modified-Since support

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

stack updated HBASE-493:
------------------------

    Fix Version/s:     (was: 0.20.0)
                   0.21.0

Moving out.  We have lots of the pieces but no one is working on this currently that I know of (correct me if I'm wrong).

> Write-If-Not-Modified-Since support
> -----------------------------------
>
>                 Key: HBASE-493
>                 URL: https://issues.apache.org/jira/browse/HBASE-493
>             Project: Hadoop HBase
>          Issue Type: New Feature
>          Components: client, io, regionserver
>            Reporter: Chris Richard
>            Priority: Minor
>             Fix For: 0.21.0
>
>
> Write-If-Not-Modified-Since for optimistic concurrency control:
> Client retrieves cell (or row) and stores timestamp.
> Client writes to same cell (or row) and passes timestamp.
> If the cell's (or row's) latest timestamp matches the passed timestamp, the write succeeds. If the timestamps do not match, the write fails and the client is notified. The client must re-retrieve the cell/row to get the latest timestamp before attempting to write back.
> This behavior would be optional, if the client doesn't pass a timestamp to the write method, no modified check would be enforced.
> Note: blocked behind HBASE-489 due to requirement that client be able to access timestamp values.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.