Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 2 Oct 2012 14:19:09 +1100 (NCT)
From: "Cheng Hao (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <812092830.152820.1349147949157.JavaMail.jiratomcat@arcas>
In-Reply-To: <1509615013.91956.1347970447665.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (HBASE-6805) Extend co-processor framework to
 provide observers for filter operations
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Cheng Hao commented on HBASE-6805:
----------------------------------

Thank you Andrew for the clarity.
I added unit test (examples) in the new patch file. Hope it could help to understand the motive of adding the interface, and I will provide the performance test report later.
                
> 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
>         Attachments: extend_coprocessor.patch
>
>
> 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