[
https://issues.apache.org/jira/browse/HBASE-11634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14378121#comment-14378121
]
Nick Dimiduk commented on HBASE-11634:
--------------------------------------
bq. If the client is doing a read-modify-write purely on the client side, there
is not much we can do since we cannot control the application logic.
What we _could_ do is disable all non-atomic mutation operations on timeline
tables. It's harsh, but...
> 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.3.4#6332)
