[
https://issues.apache.org/jira/browse/HBASE-25190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215052#comment-17215052
]
Michael Stack commented on HBASE-25190:
---------------------------------------
Poking around, other candidates easy to move:
* Bulk load tool (will need to make the hbase-mapreduce depend on hbase-tool)
and tests
* CreateSnapshot
* hbck1 and supporting classes and tests
* HBaseConfTool
* GetJavaProperty
* RegionMover and tests
* DumpRegionServerMetrics...
I didnt' check all tools... but about 10 or or so tools w/ maybe 40 files total
and ~ ten test suites (rough count). This could be done easy enough.
Stuff like canarytool are more entrenched and will take moving out the webapps
first before they could be moved.
> Create an hbase-tool module and move here standalone tools bundled with core
> ----------------------------------------------------------------------------
>
> Key: HBASE-25190
> URL: https://issues.apache.org/jira/browse/HBASE-25190
> Project: HBase
> Issue Type: Improvement
> Components: tooling
> Reporter: Michael Stack
> Priority: Major
>
> HBASE-23933 is about moving balancer classes to a new hbase-balancer module
> as an effort at shrinking the size of the hbase-server module -- it is too
> big.
> This issue is about creating a hbase-tool module into which we'd move
> standalone tools that ship with hbase core such as the bulkloadtool and the
> canary and all related supporting and test classes.
> I do not see this making much of a dent in the size of hbase-server. This
> issue is offered as a small improvement.
> (Aside, I'd move some favored node 'tool' classes that are currently in limbo
> here at least until we rule on whether to finish or remove if this module was
> put in place -- see HBASE-25185).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
