You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (Jira)" <ji...@apache.org> on 2020/11/04 09:56:00 UTC
[jira] [Updated] (HBASE-25210) RegionInfo.isOffline is now a
duplication with RegionInfo.isSplit
[ https://issues.apache.org/jira/browse/HBASE-25210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Duo Zhang updated HBASE-25210:
------------------------------
Component/s: meta
> RegionInfo.isOffline is now a duplication with RegionInfo.isSplit
> -----------------------------------------------------------------
>
> Key: HBASE-25210
> URL: https://issues.apache.org/jira/browse/HBASE-25210
> Project: HBase
> Issue Type: Improvement
> Components: meta
> Reporter: Duo Zhang
> Assignee: niuyulin
> Priority: Major
> Fix For: 3.0.0-alpha-1
>
>
> The only place, where we set it to true is in splitRegion, and at the same time we will set split to true.
> So in general, I suggest that we deprecated isOffline and isSplitParent in RegionInfo, only leave the isSplit method. And in RegionInfoBuilder, we deprecated setOffline and only leave the setSplit method.
> This could make our code base cleaner.
> And for serialization compatibility, we'd better still keep the split and offline fields in the actual RegionInfo datastructure for a while.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)