[
https://issues.apache.org/jira/browse/HBASE-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754316#action_12754316
]
ryan rawson commented on HBASE-1723:
------------------------------------
'setTimeStamp' says 'retrieve values AT this exact timestamp'. When I Was
fixing the thrift tests, the tests suggested that the API was 'retrieve me a
vision of the past that is at this timestamp' which implies
'setTimeRange(0,providedTimestamp)'.
Retrieving exactly TS=X is rarely correct behaviour since you rely on
millisecond precise matching, and unless you are using explicit TS, its fairly
unlikely this will match. Whereas saying 'all cells older than TS=X' works much
better.
> getRowWithColumnsTs changed behavior
> ------------------------------------
>
> Key: HBASE-1723
> URL: https://issues.apache.org/jira/browse/HBASE-1723
> Project: Hadoop HBase
> Issue Type: Bug
> Components: thrift
> Affects Versions: 0.20.0
> Reporter: Matthias Lehmann
> Assignee: Tim Sell
> Fix For: 0.20.1
>
> Attachments: HBASE-1723-no-rearrangement.patch, HBASE-1723-v2.patch,
> HBASE-1723.patch
>
>
> The method getRowWithTimestampTs of the thrift interface changed behavior
> from version 0.19 to 0.20:
> In 0.19, it returned only cells with exactly the given timestamp, 0.20 it to
> returns cells with a timestamp before (not including) the given timestamp.
> It needs to be clearified, which one is the desired behavior.
> I attach a patch to make 0.20 conform with 0.19 (only return cells with
> exactly the given timestamp), if this is what is wanted.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
