[
https://issues.apache.org/jira/browse/HBASE-22843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16906416#comment-16906416
]
Sakthi commented on HBASE-22843:
--------------------------------
Yes, Stack. for #1 we need a change in hbase (let me put up a patch for it
asap), for #2 & #3 we can do off with hbase-operator-tools itself. So should
the change for hbase repo be separate jira? or can I just refer to that also as
HBASE-22843 (i.e. this one. that way in both repos we would have two different
commits under same reference Jira).
> [HBCK2] Fix HBCK2 after HBASE-22777 & HBASE-22758
> -------------------------------------------------
>
> Key: HBASE-22843
> URL: https://issues.apache.org/jira/browse/HBASE-22843
> Project: HBase
> Issue Type: Sub-task
> Components: hbase-operator-tools
> Reporter: Sakthi
> Assignee: Sakthi
> Priority: Blocker
>
> There were few changes made in HBASE-22777 & HBASE-22758, which would require
> their propogation to HBCK2 as well to prevent compilation issues. These are
> the ones:
> 1. MetaTableAccessor#makePutFromTableState was changed from public to
> private. HBCK2 uses it in HBaseFsck#generatePuts() for rebuildMeta(). We
> either need to revert the change to public or make similar adjustments in
> HBCK2.
> 2.
> {code:java}
> -PairOfSameType<RegionInfo> getMergeRegions(Result data)
> +List<RegionInfo> getMergeRegions(Cell[] cells){code}
> Due to this change, HBaseFsck was fixed accordingly but not HBCK2. Let's do
> it there as well.
> 3. MetaTableAccessor#deleteRegion() was renamed to
> MetaTableAccessor#deleteRegionInfo(). Even this should be integrated with
> HBCK2.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
