hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HBASE-1831) Scanning API must be reworked to allow for fully functional Filters client-side
Date Mon, 05 Oct 2009 23:37:31 GMT

     [ https://issues.apache.org/jira/browse/HBASE-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Purtell updated HBASE-1831:
----------------------------------

    Attachment: 1831-v6.patch

Testing this now. There were two rejects against latest SVN 0.20, one in HTable, one in HConnectionManager.
I fixed them up and attached the result as -v6

> 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
>
>         Attachments: 1831-v2.patch, 1831-v3.patch, 1831-v4.patch, 1831-v5.patch, 1831-v6.patch,
1831.patch
>
>
> 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.


Mime
View raw message