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

Anoop Sam John edited comment on HBASE-18747 at 10/13/17 9:36 AM:
------------------------------------------------------------------

This preFlush hook some way same as postFlushScannerOpen . correct?  Dont know 
why we did not go the same way of pre/post hooks.  These 2 pre hooks are 
confusing IMO.  First seeing the patch, I though u r doing some thing wrong as 
pre hook is been used for the wrap op.  Later after reading where we call these 
hook, then only realized the diff.  Should be change now to follow same way of 
pre/postFlushScannerOpen?  Same for compaction case also. Just asking. Not 
related to this Jira any way.


was (Author: anoop.hbase):
This preFlush hook some way same as postFlushScannerOpen . correct?

> 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)

Reply via email to