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

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.98.0, 0.95.2, 0.94.10
• Component/s: Scanners
• Hadoop Flags: Reviewed

Release Note

"Raw" scans (Scan.setRaw(true)), now honor the scan's time range if specified.
Previously the time range would be ignored.

• Assignee: Lars Hofhansl
• Reporter: Vasu Mariyala
• Created: 26/Jun/13 18:57
• Updated: 28/Jul/13 05:34
• Resolved: 01/Jul/13 15:58

Description

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.