[jira] [Resolved] (KUDU-1733) Document Consistency Semantics

["Todd Lipcon (JIRA)" <ji...@apache.org>]

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

Todd Lipcon resolved KUDU-1733.
-------------------------------
          Resolution: Fixed
       Fix Version/s: 1.2.0
    Target Version/s:   (was: 1.3.0)

Calling this resolved by the above-mentioned review, which went into 1.2. We can always improve it in a later JIRA.

> Document Consistency Semantics
> ------------------------------
>
>                 Key: KUDU-1733
>                 URL: https://issues.apache.org/jira/browse/KUDU-1733
>             Project: Kudu
>          Issue Type: Sub-task
>          Components: client, tablet, tserver
>    Affects Versions: 1.0.1
>            Reporter: David Alves
>            Assignee: Todd Lipcon
>            Priority: Critical
>             Fix For: 1.2.0
>
>
> As per the discussion on the scope doc of the consistent operations jira (KUDU-430) we're unlikely to have an isolation/consistency mode that people can select on the client or the server. Instead we'll continue with the current approach of setting scanner modes and timestamps (though ReplicaSelection will no longer have an impact on consistency semantics).
> In light of this we should update the documentation to enlighten users on which semantics they can expect to obtain with each set of options.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)