[
https://issues.apache.org/jira/browse/HBASE-26587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472820#comment-17472820
]
Duo Zhang commented on HBASE-26587:
-----------------------------------
It is much complicated than I thought if we want to consider all the prossible
situations, for example
1. We could also change the family SFT implementation along when changing the
table level SFT implementation, and we could even only change the family SFT
implementation.
2. We already have the expected SFT implementation for some of the families,
but not all.
3. The table or family may have already have a MIGRATION SFT, and whether the
dst impl is already the exepcted one can lead to different ways to arrive the
exepcted SFT implementation.
Anyway, if we want to make our users' life easier, we should try to cover these
complexities...
Will report back laster once I have done...
Thanks.
> 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
> Assignee: 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)
