[
https://issues.apache.org/jira/browse/HBASE-29638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18028085#comment-18028085
]
Peter Somogyi commented on HBASE-29638:
---------------------------------------
Issue 1 has been resolved via HBASE-29635.
Issues 2 and 4 are straightforward to implement.
For HBaseTestingUtility compatibility, we can extract and duplicate the
required method from HBTU into the operators-tools to eliminate the direct
dependency.
The primary technical challenge - that I haven't mentioned before - remains the
replication-related commands within hbase-operator-tools, specifically
maintaining backward compatibility across both HBase 2.x and HBase 3.x branches.
> HBCK incompatibilities with HBase 3.0
> -------------------------------------
>
> Key: HBASE-29638
> URL: https://issues.apache.org/jira/browse/HBASE-29638
> Project: HBase
> Issue Type: Bug
> Components: hbase-operator-tools
> Affects Versions: hbase-operator-tools-1.3.0
> Reporter: Peter Somogyi
> Priority: Major
>
> HBCK2 is not compatible with hbase-3.0-beta-1 release.
> * scheduleRecoveries uses Hbck.scheduleServerCrashProcedure instead of the
> new scheduleServerCrashProcedures.
> * TableReporter uses Scan.setStartRow/setStopRow
> * HBaseFsck relies on HBaseTestingUtility.
> * HBaseFsck uses HRegionInfo
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
