Description
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.
Attachments
Attachments
Issue Links
- is related to
-
KUDU-1704 Add a new read mode to perform bounded staleness snapshot reads
- Resolved