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

Posted to issues@kudu.apache.org by "David Alves (JIRA)" <ji...@apache.org> on 2016/10/14 19:37:20 UTC

[jira] [Updated] (KUDU-1189) On reads at a snapshot that touch multiple tablets, without the user setting a timestamp, use the timestamp from the first server for following scans

     [ https://issues.apache.org/jira/browse/KUDU-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Alves updated KUDU-1189:
------------------------------
    Target Version/s: GA  (was: Backlog)

> On reads at a snapshot that touch multiple tablets, without the user setting a timestamp, use the timestamp from the first server for following scans
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: KUDU-1189
>                 URL: https://issues.apache.org/jira/browse/KUDU-1189
>             Project: Kudu
>          Issue Type: Sub-task
>          Components: client
>    Affects Versions: Public beta
>            Reporter: David Alves
>            Assignee: David Alves
>            Priority: Critical
>
> When performing a READ_AT_SNAPSHOT, we allow not to set a timestamp, meaning the server will pick a time. If the scan touches multiple tablets, however, we don't set the timestamp assigned to the first scan on the other scans, meaning each scan will have it's own timstamp, which is wrong.



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