You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Nick Dimiduk (JIRA)" <ji...@apache.org> on 2014/07/31 21:36:39 UTC
[jira] [Created] (HBASE-11634) Disallow non-atomic update
operations when TIMELINE consistency is enabled
Nick Dimiduk created HBASE-11634:
------------------------------------
Summary: Disallow non-atomic update operations when TIMELINE consistency is enabled
Key: HBASE-11634
URL: https://issues.apache.org/jira/browse/HBASE-11634
Project: HBase
Issue Type: Improvement
Components: Client, Usability
Affects Versions: 0.99.0, hbase-10070
Reporter: Nick Dimiduk
Something to consider for the HBASE-10070 line of changes. When a client reads a timeline consistent view of data, read-update-write operations are potentially destructive. When a client is accepting TIMELINE reads, we should only allow server-side atomic update operations.
In a future state, we could offer a CRDT-based data type to further extend the set of write operations that are guaranteed safe under this consistency model.
I may not have the semantics of the new client API correct, but this is the idea: do what we can to protect users from the major dangers of this relaxed consistency model.
--
This message was sent by Atlassian JIRA
(v6.2#6252)