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

Todd Lipcon reassigned KUDU-1733:
---------------------------------

    Assignee: Todd Lipcon  (was: David Alves)

> 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
>
> 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.4#6332)

Reply via email to