You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Vasu Mariyala (JIRA)" <ji...@apache.org> on 2013/06/26 20:59:19 UTC

[jira] [Created] (HBASE-8809) Include deletes in the scan (setRaw) method does not respect the time range or the filter

Vasu Mariyala created HBASE-8809:
------------------------------------

             Summary: 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


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

      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;
      }

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