hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8809) Include deletes in the scan (setRaw) method does not respect the time range or the filter
Date Sat, 06 Jul 2013 13:17:48 GMT

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

Hudson commented on HBASE-8809:
-------------------------------

Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #602 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/602/])
    HBASE-8809 test fix (Revision 1500232)
HBASE-8809 Addendum to correctly hand versions in raw scans aswell (Jesse and LarsH) (Revision
1500217)

     Result = FAILURE
larsh : 
Files : 
* /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestKeepDeletes.java

larsh : 
Files : 
* /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/ScanQueryMatcher.java
* /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestFromClientSide.java

                
> Include deletes in the scan (setRaw) method does not respect the time range or the filter
> -----------------------------------------------------------------------------------------
>
>                 Key: HBASE-8809
>                 URL: https://issues.apache.org/jira/browse/HBASE-8809
>             Project: HBase
>          Issue Type: Bug
>          Components: Scanners
>            Reporter: Vasu Mariyala
>            Assignee: Lars Hofhansl
>             Fix For: 0.98.0, 0.95.2, 0.94.10
>
>         Attachments: 8806-trunk-addendum.txt, 8809-0.94.txt, 8809-trunk.txt, DeleteMarkers.doc,
hbase-8809-0.94-addendum-example.patch, hbase-8809-addendum-0.94-v0.patch
>
>
> If a row has been deleted at time stamp 'T' and a scan with time range (0, T-1) is executed,
it still returns the delete marker at time stamp 'T'. It is because of the code in ScanQueryMatcher.java
> {code}
>       if (retainDeletesInOutput
>           || (!isUserScan && (EnvironmentEdgeManager.currentTimeMillis() - timestamp)
<= timeToPurgeDeletes)
>           || kv.getMemstoreTS() > maxReadPointToTrackVersions) {
>         // always include or it is not time yet to check whether it is OK
>         // to purge deltes or not
>         return MatchCode.INCLUDE;
>       }
> {code}
> The assumption is scan (even with setRaw is set to true) should respect the filters and
the time range specified.
> Please let me know if you think this behavior can be changed so that I can provide a
patch for it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message