hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Richard (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HBASE-493) Write-If-Not-Modified-Since support
Date Wed, 05 Mar 2008 19:03:41 GMT

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

Chris Richard updated HBASE-493:
--------------------------------

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



  was:
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 not-modified check will be enforced.

Note: requires HBASE-489 to be complete, in order for the client to be able to access timestamp
values.




> 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.2.0
>            Reporter: Chris Richard
>
> 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.


Mime
View raw message