You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2010/04/13 18:27:17 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 ]

Andrew Purtell updated HBASE-493:
---------------------------------

    Status: Open  (was: Patch Available)

Cancelling stale patch. 

> 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
>    Affects Versions: 0.21.0
>            Reporter: Chris Richard
>            Priority: Minor
>             Fix For: 0.21.0
>
>         Attachments: HBASE-493.patch
>
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira