You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Guanghao Zhang (JIRA)" <ji...@apache.org> on 2019/07/11 02:15:00 UTC

[jira] [Comment Edited] (HBASE-22673) Avoid to expose protobuf stuff in Hbck interface

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

Guanghao Zhang edited comment on HBASE-22673 at 7/11/19 2:14 AM:
-----------------------------------------------------------------

For getFailedSplitMergeLegacyRegions method, I thought we should remove it in future. The Hbck interface should only support method which about "fixing". The "checking" work can be done by HBCK1 or master. We can add a chore thread in master to check the wrong thing. And show them in master web ui.


was (Author: zghaobac):
For getFailedSplitMergeLegacyRegions method, I thought we should remove it in future. The Hbck interface should only support method which about "fixing". The "checking" work can be done by HBCK1. And we should add a chore thread in master to check the wrong thing. And show them in master web ui.

> Avoid to expose protobuf stuff in Hbck interface
> ------------------------------------------------
>
>                 Key: HBASE-22673
>                 URL: https://issues.apache.org/jira/browse/HBASE-22673
>             Project: HBase
>          Issue Type: Improvement
>          Components: hbck2
>            Reporter: Guanghao Zhang
>            Assignee: Guanghao Zhang
>            Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)