[
https://issues.apache.org/jira/browse/HBASE-3991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050008#comment-13050008
]
Todd Lipcon commented on HBASE-3991:
------------------------------------
Here are my opinions:
- writing scripts in ruby is convenient but not very maintainable since only a
few of the committers actually know Ruby. they also don't really integrate with
the test suite very well.
- if you write the tools in Java, there should be at least minimal unit tests
that make sure they work
- if in Java, maybe we would want them to all go in from the same command line?
eg "hbase tool hfile-stats <...>"?
If it's truely a bunch of random one-off tools and scripts, something like a
github project "hbase toolkit" would make more sense?
> Add Util folder for Utility Scripts
> -----------------------------------
>
> Key: HBASE-3991
> URL: https://issues.apache.org/jira/browse/HBASE-3991
> Project: HBase
> Issue Type: Brainstorming
> Components: scripts, util
> Affects Versions: 0.92.0
> Reporter: Nicolas Spiegelberg
> Assignee: Nicolas Spiegelberg
>
> This JIRA is to start discussion around adding some sort of 'util' folder to
> HBase for common operational scripts. We're starting to write a lot of HBase
> analysis utilities that we'd love to share with open source, but don't want
> to clutter the 'bin' folder, which seems like it should be reserved for
> start/stop tasks. If we add a 'util' folder, how do we keep it from becoming
> a cesspool of half-baked & duplicated operational hacks.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
