[
https://issues.apache.org/jira/browse/HBASE-18169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16141205#comment-16141205
]
stack commented on HBASE-18169:
-------------------------------
bq. How do we deal with this? Wrapping an InternalScanner can only do
filtering, should we give user the ability to change the read point, and also
the ScanType, from RETAIN_DELETE to DROP_DELETE? Anyway, I do not think we
should let user create StoreScanner directly.
No. They cannot change readpoint. We'll have to expose even more internals for
them to do that. They won't know what they are doing anyways (smile).
Agree on removing create.
> Coprocessor fix and cleanup before 2.0.0 release
> ------------------------------------------------
>
> Key: HBASE-18169
> URL: https://issues.apache.org/jira/browse/HBASE-18169
> Project: HBase
> Issue Type: Improvement
> Components: Coprocessors
> Affects Versions: 2.0.0-alpha-1
> Reporter: Duo Zhang
> Priority: Blocker
> Fix For: 2.0.0-alpha-3
>
>
> As discussed in HBASE-18038. In RegionServerServices, Region and StoreFile
> interfaces we expose too many unnecessary methods. We need to find a way to
> not expose these methods to CP.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
