hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anoop Sam John (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HBASE-18169) Coprocessor fix and cleanup before 2.0.0 release
Date Thu, 19 Oct 2017 10:32:00 GMT

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

Anoop Sam John edited comment on HBASE-18169 at 10/19/17 10:31 AM:
-------------------------------------------------------------------

preWALRestore and postWALRestore having a WALKey param which is  IA.Private.  This has to
handled. [~Apache9]  , [~stack]..   Did not check in detail what this can expose to CP users
and what all are needed really.  Just adding here while I was going through RegionObserver

Same issue in WALObserver preWALWrite and postWALWrite


was (Author: anoop.hbase):
preWALRestore and postWALRestore having a WALKey param which is  IA.Private.  This has to
handled. [~Apache9]  , [~stack]..   Did not check in detail what this can expose to CP users
and what all are needed really.  Just adding here while I was going through RegionObserver

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

Mime
View raw message