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

Duo Zhang commented on HBASE-18446:
-----------------------------------

{quote}
Should mark co processors also in the Limited private.
{quote}
No. I do not think we should expose {{StoreFileScanner}} and 
{{StoreFileReader}} to CP users. I think for most cases filtering on the final 
RegionScanner is enough, and it is dangerous to create a custom store file 
level scanner as our correctness highly depends on the complicated SQM which is 
evaluated after fetching kvs from store file level scanner.

{quote}
So you suggest we remove these hooks (with no replacement) later for 3.0?
{quote}
It depends on when do we find another way to support the Phoenix secondary 
index. It will be good if we can remove them in 2.0.0. [~stack] is helping 
currently.

Thanks.

> Mark StoreFileScanner/StoreFileReader as IA.LimitedPrivate(Phoenix)
> -------------------------------------------------------------------
>
>                 Key: HBASE-18446
>                 URL: https://issues.apache.org/jira/browse/HBASE-18446
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Coprocessors
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Critical
>             Fix For: 2.0.0-alpha-3
>
>         Attachments: HBASE-18446.patch
>
>
> Do not see any reason why it is marked as IA.LimitedPrivate. It is not 
> referenced in any CPs.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to