You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Hao Hao (JIRA)" <ji...@apache.org> on 2018/03/14 23:27:00 UTC

[jira] [Commented] (KUDU-1704) Add a new read mode to perform bounded staleness snapshot reads

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

Hao Hao commented on KUDU-1704:
-------------------------------

Fixed in commits 723ced836, 5047f091d, 0c05e8375, 48cdaaa17.

> Add a new read mode to perform bounded staleness snapshot reads
> ---------------------------------------------------------------
>
>                 Key: KUDU-1704
>                 URL: https://issues.apache.org/jira/browse/KUDU-1704
>             Project: Kudu
>          Issue Type: Sub-task
>          Components: client
>    Affects Versions: 1.1.0
>            Reporter: David Alves
>            Assignee: Hao Hao
>            Priority: Major
>              Labels: consistency
>
> It would be useful to be able to perform snapshot reads at a timestamp that is higher than a client provided timestamp, thus improving recency, but lower that the server's oldest inflight transaction, thus minimizing the scan's chance to block.
> Such a mode would not guarantee linearizability, but would still allow for client-local read-your-writes, which seems to be one of the properties users care about the most.
> This should likely be the new default read mode for scanners.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)