[
https://issues.apache.org/jira/browse/HBASE-18747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16203300#comment-16203300
]
Anoop Sam John commented on HBASE-18747:
----------------------------------------
Do we really need to expose the new Filter and the Wrapper to CPs now? They
can do this work on their own right? Can use preFlush/preCompact and there we
pass the actual scanner used while doing the flush/compaction. They can return
a wrapper impl and first the cells will flow in there and they can do their
logic. I dont think we need give this filter. This will only confuse with the
client side filters. I agree these are just helpers. Or else can just move
them to the example module itself.
> Introduce new example and helper classes to tell CP users how to do filtering
> on scanners
> -----------------------------------------------------------------------------------------
>
> Key: HBASE-18747
> URL: https://issues.apache.org/jira/browse/HBASE-18747
> Project: HBase
> Issue Type: Sub-task
> Components: Coprocessors
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Critical
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-18747.patch
>
>
> Finally we decided that CP users should not have the ability to create
> {{StoreScanner}} or {{StoreFileScanner}}, so it is impossible for them to
> filter out some cells when flush or compaction by simply provide a filter
> when constructing {{StoreScanner}}.
> But I think filtering out some cells is a very important usage for CP users,
> so we need to provide the ability in another way. Theoretically it can be
> done with wrapping an {{InternalScanner}}, but I think we need to give an
> example, or even some helper classes to help CP users.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
