You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org> on 2016/06/23 22:32:16 UTC

[jira] [Commented] (KUDU-1498) Add support to Java client for read-your-writes consistency

    [ https://issues.apache.org/jira/browse/KUDU-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15347331#comment-15347331 ] 

Jean-Daniel Cryans commented on KUDU-1498:
------------------------------------------

Right now the Java client is always reading from the leader, so all you need is READ_AT_SNAPSHOT.

> Add support to Java client for read-your-writes consistency
> -----------------------------------------------------------
>
>                 Key: KUDU-1498
>                 URL: https://issues.apache.org/jira/browse/KUDU-1498
>             Project: Kudu
>          Issue Type: Sub-task
>          Components: client
>            Reporter: Mike Percy
>
> The Java client could use a mode called "read your writes" consistency where we ensure that we read whatever the leader has committed at the time of the request.
> At the time of writing, the implementation requirements look like the following:
> * Always scan from the leader
> * Specify that the leader must apply all operations from previous leaders before processing the query
> In the C++ client, this can be achieved by specifying both of the LEADER_ONLY and READ_AT_SNAPSHOT options, while not specifying a timestamp to use for the snapshot when starting the scan.
> In the Java client API, we may want to simply expose a scan option called "read your writes" or something similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)