You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Nick Dimiduk (JIRA)" <ji...@apache.org> on 2014/07/31 21:38:39 UTC
[jira] [Updated] (HBASE-11634) Disallow non-atomic update
operations when TIMELINE consistency is enabled
[ https://issues.apache.org/jira/browse/HBASE-11634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Dimiduk updated HBASE-11634:
---------------------------------
Issue Type: Sub-task (was: Improvement)
Parent: HBASE-10070
> 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: Sub-task
> 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)