[
https://issues.apache.org/jira/browse/KUDU-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16399865#comment-16399865
]
Hao Hao commented on KUDU-1704:
-------------------------------
Hmm, I guess I used my local commit hash. Just verified it should be 9d233f457
instead.
I think the description in the jira does not specifically mentioned it is
snapshot consistency across all tablets. Though it did mention it is bounded
staleness. Currently, there is no API to specify the staleness bound yet.
So to make it more clear, I linked the design doc and will update the
description and file a follow up Jira to add a API to specify the staleness
bound.
> 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
> Fix For: 1.7.0
>
>
> 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)
