[
https://issues.apache.org/jira/browse/HBASE-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758847#action_12758847
]
stack commented on HBASE-1831:
------------------------------
On 3., above, carrying stateful filters across regions, it can't be done easily
in 0.20.x because we can get a NotServingRegionException at any time. Also, if
nothing goes wrong and we just exhaust a scanner on a particular region, the
last thing done over in RegionServer is cleanup of scanner so a subsequent
getFilter call would have nothing to pick up on once it'd arrived at the
RegionServer. Statefulness has to be done client-side; filters need to allow
specifying a client-component.
> Scanning API must be reworked to allow for fully functional Filters
> client-side
> -------------------------------------------------------------------------------
>
> Key: HBASE-1831
> URL: https://issues.apache.org/jira/browse/HBASE-1831
> Project: Hadoop HBase
> Issue Type: Bug
> Affects Versions: 0.20.0
> Reporter: Jonathan Gray
> Priority: Critical
> Fix For: 0.20.1, 0.21.0
>
>
> Right now, a client replays part of the Filter locally by calling
> filterRowKey() and filterAllRemaining() to determine whether it should
> continue to the next region.
> A number of new filters rely on filterKeyValue() and other calls to alter
> state. It's also a false assumption that all rows/keys affecting a filter
> returning true for FAR will be seen client-side (what about those that failed
> the filter).
> This issue is about dealing with Filters properly from the client-side.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
