[
https://issues.apache.org/jira/browse/HBASE-21393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16668204#comment-16668204
]
stack commented on HBASE-21393:
-------------------------------
Oh. You want to import protobuf? Its to make the ServerName as pb? Dang. I told
you do that. I think I made a mistake.
The below protos are for hbase internals only:
import org.apache.hadoop.hbase.shaded.protobuf.generated.HBaseProtos;
If the server-side was String instead of ServerName, you wouldn't have to have
the hbase internals on the client-side? That might be better? Loose-coupling.
Using guava is probably not so bad only you don't say what version of guava we
are to use here in hbck2. We seem to be transitively depending on what is on
the CLASSPATH? When hbck2 is on same classpath as hbase and hadoop, it might
cause pain. Have to have the hbck dependencies come first.
> Add an API ScheduleSCP() to HBCK2
> ----------------------------------
>
> Key: HBASE-21393
> URL: https://issues.apache.org/jira/browse/HBASE-21393
> Project: HBase
> Issue Type: Sub-task
> Components: hbase-operator-tools, hbck2
> Reporter: Jingyun Tian
> Assignee: Jingyun Tian
> Priority: Major
> Attachments: 0001-HBASE-21393-Add-an-API-ScheduleSCP-to-HBCK2.patch
>
>
> Add the API of ScheduleSCP() to hbase-operator-tools so that operators can
> schedule ServerCrashProcedures of specified regionservers.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
