[
https://issues.apache.org/jira/browse/HBASE-6805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13468276#comment-13468276
]
Andrew Purtell commented on HBASE-6805:
---------------------------------------
[~jason.dai] How would coprocessors register themselves onto the separate
lists? Would this be done with e.g. @annotations? In my opinion, I think we
need a compelling use case to add this kind of complexity to an API, even the
CP API. If there is no way to accomplish what you might want to do, then it's
clear we have to consider CP API modifications, and then consider the
performance implications, etc. However Gary's suggestions above seem reasonable
alternative approaches.
We should prefer the simplest approach possible in API and integration design
(but no simpler). If there's a compelling reason to do this, then we can for
sure consider it, but please consider Gary's thoughts above. So far it would
appear the case for filter CP hooks isn't compelling because there is a design
alternative that seems reasonable. Would his suggestions work for you? If not,
why not? That would be a great way forward with this discussion.
> 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
