David Alves commented on KUDU-577:

The current thinking is that instead of having blanket isolation/consistency 
modes, we'll have "recipes" on how to get them. This leaves the door open to 
new trade-offs in the future without forcing us to drop or change the supported 
isolation/consistency modes.

For instance, we'll document how to get strict-serializability, how to just get 
serializability + (client/session local) read-your-writes, or how users can 
just disregard consistency/latency altogether if they prefer to optimize for 

> Specification for expected semantics and client modes
> -----------------------------------------------------
>                 Key: KUDU-577
>                 URL: https://issues.apache.org/jira/browse/KUDU-577
>             Project: Kudu
>          Issue Type: Sub-task
>          Components: api, client
>    Affects Versions: M4.5
>            Reporter: Jean-Daniel Cryans
>            Priority: Critical
> We need a detailed description of what the different client modes are and 
> what it means the clients should do. This is to ensure that both terminology 
> and behavior match between languages.

This message was sent by Atlassian JIRA

Reply via email to