[ https://issues.apache.org/jira/browse/KUDU-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890992#comment-15890992 ]
Todd Lipcon commented on KUDU-1813: ----------------------------------- [~dralves] do you have an opinion on this one? > Scan at a specific timestamp doesn't include that timestamp as committed > ------------------------------------------------------------------------ > > Key: KUDU-1813 > URL: https://issues.apache.org/jira/browse/KUDU-1813 > Project: Kudu > Issue Type: Bug > Components: tablet > Affects Versions: 1.2.0 > Reporter: Todd Lipcon > Assignee: Todd Lipcon > Priority: Critical > > Currently, if the user performs the following sequence: > - Insert a row > - ts = client_->GetLastObservedTimestamp() > - create a new scanner with READ_AT_SNAPSHOT set to 'ts' > they will not observe their own write. This seems to be due to incorrect > usage of MvccSnapshot(ts) constructor which says that it considers all writes > _before_ 'ts' to be committed, rather than _before or equal to_. -- This message was sent by Atlassian JIRA (v6.3.15#6346)