You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Alexey Serbin (JIRA)" <ji...@apache.org> on 2016/09/29 20:01:20 UTC

[jira] [Created] (KUDU-1664) Clean-up in-code documentation for KuduScanner::ReadMode and KuduClient::GetLatestObservedTimestamp

Alexey Serbin created KUDU-1664:
-----------------------------------

             Summary: Clean-up in-code documentation for KuduScanner::ReadMode and KuduClient::GetLatestObservedTimestamp
                 Key: KUDU-1664
                 URL: https://issues.apache.org/jira/browse/KUDU-1664
             Project: Kudu
          Issue Type: Bug
          Components: api, client, documentation
    Affects Versions: 1.0.0
            Reporter: Alexey Serbin
            Priority: Minor


After reading the in-line doc for the subj. entities, one would expect the scanner from the following code to do its job on reading-what-you-have-written:

{code}
const uint64_t snapshot_timestamp = client->GetLatestObservedTimestamp();

KuduScanner scanner(table.get());
RETURN_NOT_OK(scanner.SetSnapshotRaw(snapshot_timestamp));
RETURN_NOT_OK(scanner.SetReadMode(KuduScanner::READ_AT_SNAPSHOT));
RETURN_NOT_OK(scanner.Open());
{code}

However, it does not work.

To make it work, it's necessary to add extra 1 to the snapshot timestamp:

{code}
RETURN_NOT_OK(scanner.SetSnapshotRaw(snapshot_timestamp + 1));
{code}



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