hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Reopened: (HBASE-493) Write-If-Not-Modified-Since support
Date Sat, 18 Oct 2008 05:14:46 GMT

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

stack reopened HBASE-493:

Reopening.  Row locks prevent others from writing a row.  Whats asked for is if the cell has
not been modified since a particular read, only then commit the write (Needed if you were
going to do something like appengine.  Also a feature of yahoo's peanuts).

> 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.18.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

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

View raw message