hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6805) Extend co-processor framework to provide observers for filter operations
Date Thu, 20 Sep 2012 18:06:08 GMT

    [ https://issues.apache.org/jira/browse/HBASE-6805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13459810#comment-13459810

Andrew Purtell commented on HBASE-6805:

[~jason.dai] Regarding your point 1, that sounds reasonable. 

For point 2, filter wrapping from scanner creation is something the current API supports,
so you should be good there.

For point 3, I'm not sure I understand, if you have wrapped a scanner, why you then need to
call out to (or receive upcalls on) filter observer hooks, but perhaps your patch will make
it clear. To assist with this understanding, please consider providing a small example of
filter+scan wrapping? See (on trunk) hbase-server/src/main/java/org/apache/hadoop/hbase/coprocessor/example/
for other such examples.
> Extend co-processor framework to provide observers for filter operations
> ------------------------------------------------------------------------
>                 Key: HBASE-6805
>                 URL: https://issues.apache.org/jira/browse/HBASE-6805
>             Project: HBase
>          Issue Type: Sub-task
>          Components: coprocessors
>    Affects Versions: 0.96.0
>            Reporter: Jason Dai
> There are several filter operations (e.g., filterKeyValue, filterRow, transform, etc.)
at the region server side that either exclude KVs from the returned results, or transform
the returned KV. We need to provide observers (e.g., preFilterKeyValue and postFilterKeyValue)
for these operations in the same way as the observers for other data access operations (e.g.,
preGet and postGet). This extension is needed to support DOT (e.g., extracting individual
fields from the document in the observers before passing them to the related filter operations)

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message