[
https://issues.apache.org/jira/browse/HBASE-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590950#action_12590950
]
Clint Morgan commented on HBASE-595:
------------------------------------
The problem is that we are notifying the filters of the filtering
decision prematurely. Hstores use the filters on row key and
individual columns, but the final filtering decision does not come
until all of the stores' columns are assembled in the hregion. So only
after this decision has been made can we notify rowProcessed() to filters (in
the hregion).
I say we should patch branches.
But its probably not a big deal. Looking over existing filter impls, only
PageRowFilter would be affected by the bug. (And this filter offerers little
utility
because it only skips the rows after the page. Instead you could save
the trouble and just stop the advancing the scanner in the first
place.)
> RowFilterInterface.rowProcessed() is called *before* fhe final filtering
> decision is made
> -----------------------------------------------------------------------------------------
>
> Key: HBASE-595
> URL: https://issues.apache.org/jira/browse/HBASE-595
> Project: Hadoop HBase
> Issue Type: Bug
> Components: filters
> Affects Versions: 0.2.0, 0.1.1
> Reporter: Clint Morgan
> Attachments: hbase-595.patch
>
>
> rowProcessed is called in HStoreScanner, however, the final filtering
> decision is not made until the full row has been assembled in HRegion
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
