[
https://issues.apache.org/jira/browse/KUDU-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891345#comment-15891345
]
David Alves commented on KUDU-1411:
-----------------------------------
Most of this is solved. The java client always did timestamp propagation for
writes. Alexey fixed it for scans on 16ce5e02466a18e591672a84bc9a4bd6db7d00ea
and 2f1a2a06d4fe719ef9f35338bc7403915517718a. Dan had added timestamp
propagation when the client builds the scan tokens, but apparently we're still
missing it when the scan tokens get deserialized (i.e. setting the propagated
timestamp in pbIntoScanner).
> Implement HT timestamp propagation in the Java client
> -----------------------------------------------------
>
> Key: KUDU-1411
> URL: https://issues.apache.org/jira/browse/KUDU-1411
> Project: Kudu
> Issue Type: Improvement
> Reporter: Dan Burkert
>
> The Java client doesn't do any timestamp propagation. The ScanToken
> implementation should also be updated so that deserializing a ScanToken
> results in a propagating the timestamp of the serializer into the
> deserializer.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
