[
https://issues.apache.org/jira/browse/HBASE-6740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453675#comment-13453675
]
stack commented on HBASE-6740:
------------------------------
If you want, you could do something like Jesse suggested whereby a
non-committer could maintain a 'branch' out on github. The notion is that in
the hbase JIRA we'd add a branch that you could file issues against and fix out
on github. That way your github work gets visibility inside in the project,
you can iterate at whatever rate you want, and you don't need to go via
committer. Would that work for hbase-tools that are new not yet part of core?
As tools mature out in hbase-tools, we can bring them over. If enough of them,
we could make hbase-tools module.
> Build out a toolset to make regular user operations on HBase tables
> -------------------------------------------------------------------
>
> Key: HBASE-6740
> URL: https://issues.apache.org/jira/browse/HBASE-6740
> Project: HBase
> Issue Type: Improvement
> Reporter: Amandeep Khurana
>
> We currently have some stock MR jobs like import/export, copytable, importtsv
> etc and tools like hbck, hfile viewer, WAL viewer etc that are a part of
> HBase core. These are sometimes used just as is and often times need some
> sort of customization to make them work in user environments. I propose we
> build out a more extensive and extensible tool set and move it out to a
> separate package outside core so we can add to those and release those as
> they evolve.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
