[ https://issues.apache.org/jira/browse/HBASE-13193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Lawlor updated HBASE-13193: ------------------------------------ Attachment: HBASE-13193-v4.patch The issue with the patch applying to branch 0.94 has been called out in HBASE-13208. Re-attaching to trigger a precommit build (last attachment didn't start one) > RegionScannerImpl filters should not be reset if a partial Result is returned > ----------------------------------------------------------------------------- > > Key: HBASE-13193 > URL: https://issues.apache.org/jira/browse/HBASE-13193 > Project: HBase > Issue Type: Bug > Reporter: Jonathan Lawlor > Assignee: Jonathan Lawlor > Attachments: HBASE-13193-v1.patch, HBASE-13193-v2.patch, > HBASE-13193-v3.patch, HBASE-13193-v4.patch, HBASE-13193-v4.patch, > HBASE-13193-v4.patch > > > In RegionScannerImpl the filters get reset during calls to nextRaw: > {code} > public NextState nextRaw(List<Cell> outResults, int batchLimit, long > remainingResultSize) > throws IOException { > ... > resetFilters(); > if (isFilterDoneInternal()) { > ... > } > {code} > This creates a problem when returning partial Results because filters should > only be reset in between rows (i.e. after all of the cells for a particular > row have been returned). If a partial Result is returned, there are still > cells in the row that have not been evaluated yet and we should avoid > resetting the filter since it will wipe away all state information for that > filter. -- This message was sent by Atlassian JIRA (v6.3.4#6332)