hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Kellerman (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-613) Timestamp-anchored scanning fails to find all records
Date Wed, 18 Jun 2008 02:38:45 GMT

    [ https://issues.apache.org/jira/browse/HBASE-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12605814#action_12605814
] 

Jim Kellerman commented on HBASE-613:
-------------------------------------

I finally found the problem (I think)... not only does the supplied timestamp apply to rows
within the regions being scanned, it also applies to the regions being found in META. Thus
if you specify a timestamp that is older than some of the regions in the META, you will only
scan those regions and not all the regions in the table.This is really nasty, because you
want to use HConstants.TIMESTAMP_LATEST to scan the META, and then use the user supplied timestamp
for filtering results from scanners over those regions. Yuk!

> 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.


Mime
View raw message