hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-3991) Add Util folder for Utility Scripts
Date Wed, 15 Jun 2011 21:52:47 GMT

    [ https://issues.apache.org/jira/browse/HBASE-3991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050061#comment-13050061

stack commented on HBASE-3991:

@Nicolas What are the scripts written in?  The util would be where?  Under the bin or at top-level?

Up to now I've seen 'bin' as place for 'scripts' that up to this have been non-java but scripts
that are not actively in use have the tendency to rot especially if they do not need to be
compiled.  We have this prob. now w/ bin contents.

Regards, "...how do we keep it from becoming a cesspool of half-baked & duplicated operational
hacks", thats a tough.  Tests for scripts would help with rot.  Libs that scripts can reuse
would help mitigate duplication (the ruby stuff has libs and primitive tests that has not
been consistently exploited).

If we think the cesspool inevitable, yeah, lets move the smell elsewhere as per Todd.

> 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


View raw message