You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Jonathan Gray (JIRA)" <ji...@apache.org> on 2009/09/23 06:36:15 UTC
[jira] Commented: (HBASE-1831) Scanning API must be reworked to
allow for fully functional Filters client-side
[ https://issues.apache.org/jira/browse/HBASE-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758581#action_12758581 ]
Jonathan Gray commented on HBASE-1831:
--------------------------------------
Filters should not be run on the client-side at all.
Server needs to be able to tell whether Scan should continue to the next region or not.
> 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.