[
https://issues.apache.org/jira/browse/HBASE-26286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17435979#comment-17435979
]
Szabolcs Bukros commented on HBASE-26286:
-----------------------------------------
[~zhangduo], [~wchevreuil], [~elserj]
After checking the code, making *cloning* SFT configurable looks
straightforward enough. We can freely overwrite the Descriptors and use the new
SFT impl table wide. However the same is not true for *restore*. The store
configuration StoreEngine and SFT impl is based on is a composite of 3 sources:
master conf, TableDescriptor, ColumnFamilyDescriptor. We can not change any of
these without potentially affecting otherwise untouched stores and my
assumption is that we should avoid that.
My suggestion would be to drop restore from the scope. Because if changing
otherwise untouched regions should be avoided than our Descriptor granularity
is insufficient for this task. If changing regions untouched by restore is
acceptable, I would argue doing a traditional restore and using the already
existing migration logic is a cleaner solution than mixing it with snapshot
restore.
Am I missing something? What do you think?
> Add support for specifying store file tracker when restoring or cloning
> snapshot
> --------------------------------------------------------------------------------
>
> Key: HBASE-26286
> URL: https://issues.apache.org/jira/browse/HBASE-26286
> Project: HBase
> Issue Type: Sub-task
> Components: HFile, snapshots
> Reporter: Duo Zhang
> Assignee: Szabolcs Bukros
> Priority: Major
>
> As discussed in HBASE-26280.
> https://issues.apache.org/jira/browse/HBASE-26280?focusedCommentId=17414894&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17414894
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
