[
https://issues.apache.org/jira/browse/HBASE-6740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451070#comment-13451070
]
stack commented on HBASE-6740:
------------------------------
Hmm... what would having tools in a module do for us?
Wondering more what this means "...and often times need some sort of
customization to make them work in user environments"? This involve changes to
the core or are you finding yourself copy/pasting to add some needed facility
that you'd like to commit back and have available at a rate that is higher than
that at which we release?
I suppose this facility would be for toolsmiths to share their improvements.
Do we need to move current tools to the toolsmiths' repo? Or can they stay
where they are and toolsmiths use hbase-tools repo for new stuff or amendments
to core tools?
> 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
