[
https://issues.apache.org/jira/browse/HBASE-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606080#action_12606080
]
Jim Kellerman commented on HBASE-613:
-------------------------------------
> stack - 18/Jun/08 01:25 PM
> Do the non-first regions have cells with entries that are timestamp <=
> previous?
No. The way I calculate previous is after the first run of
PerformanceEvaluation. I scan the whole table (using latest) and take the
maximum timestamp found as previous.
Then I wait for a bit before the second run of PerformanceEvaluation (just to
be sure all the timestamps will be > previous) and that's when I run the test.
Am still trying to figure why the first region works fine but none of the
others do.
> Timestamp-anchored scanning fails to find all records
> -----------------------------------------------------
>
> Key: HBASE-613
> URL: https://issues.apache.org/jira/browse/HBASE-613
> Project: Hadoop HBase
> Issue Type: Bug
> Components: client
> Reporter: stack
> Assignee: Jim Kellerman
> Fix For: 0.2.0
>
> Attachments: nogood.patch, TestTimestampScanning.java, Timestamp.patch
>
>
> If I add 3 versions of a cell and then scan across the first set of added
> cells using a timestamp that should only get values from the first upload, a
> bunch are missing (I added 100k on each of the three uploads). I thought it
> the fact that we set the number of cells found back to 1 in HStore when we
> move off current row/column but that doesn't seem to be it. I also tried
> upping the MAX_VERSIONs on my table and that seemed to have no effect. Need
> to look closer.
> Build a unit test because replicating on cluster takes too much time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
