You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Wellington Chevreuil (Jira)" <ji...@apache.org> on 2022/01/06 15:20:00 UTC
[jira] [Commented] (HBASE-26587) Introduce a new Admin API to change SFT implementation
[ https://issues.apache.org/jira/browse/HBASE-26587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17469964#comment-17469964 ]
Wellington Chevreuil commented on HBASE-26587:
----------------------------------------------
{quote}
I would like to introduce a new procedure, which just schedule two MTP as sub procedures, one for switching from SRC to MIGRATION, and the second for switching from MIGRATION to DST.
{quote}
Looks reasonable. How about the API method definition itself? Would you think it should be generic enough for callers to specify the desired tracker implementation, or should it be specific for migrating to FILE tracker impl?
> Introduce a new Admin API to change SFT implementation
> ------------------------------------------------------
>
> Key: HBASE-26587
> URL: https://issues.apache.org/jira/browse/HBASE-26587
> Project: HBase
> Issue Type: Sub-task
> Components: Admin, API
> Reporter: Duo Zhang
> Priority: Major
>
> Now changing SFT implementation requires two MTP, and there are also lots of rules on how to correctly set the MIGRATION SFT, I think we'd better introduce a special method to implement the complicated logic by code,to make our users life easier.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)