David Alves reassigned KUDU-1679:

    Assignee: David Alves

> Propagate timestamps for scans
> ------------------------------
>                 Key: KUDU-1679
>                 URL: https://issues.apache.org/jira/browse/KUDU-1679
>             Project: Kudu
>          Issue Type: Sub-task
>          Components: tserver
>    Affects Versions: 1.0.1
>            Reporter: David Alves
>            Assignee: David Alves
> We only propagate timestamps from writes to reads, not between two reads. 
> This leaves the door open to unrepeatable read anomalies:
> If T1, T2 are reads from the same client where T2 starts after the response 
> from T1 is received and neither are assigned timestamps by the client. It 
> might be the case where T2’s observed value actually precedes T1’s value in 
> the row history if T1 and T2 are performed in different servers, as T2 can be 
> assigned a timestamp that is lower than T1.

This message was sent by Atlassian JIRA

Reply via email to