[jira] [Commented] (HBASE-6740) Build out a toolset to make regular user operations on HBase tables
[ 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
[jira] [Commented] (HBASE-6740) Build out a toolset to make regular user operations on HBase tables
[ https://issues.apache.org/jira/browse/HBASE-6740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453471#comment-13453471 ] Amandeep Khurana commented on HBASE-6740: - I think it makes sense to have a separate toolsmith's repo for ongoing work where people can keep adding tools. As those tools become stable, they can be rolled back into a hbase-tools module in the main project. This allows for faster iteration on just the tools and an independent release cycle for newer tools that folks might find useful. > 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
[jira] [Commented] (HBASE-6740) Build out a toolset to make regular user operations on HBase tables
[ https://issues.apache.org/jira/browse/HBASE-6740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451073#comment-13451073 ] stack commented on HBASE-6740: -- We could on a period review the hbase-tools repo to roll stuff back into core (this is opposite of what I said above but hey, brainstorming). > 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
[jira] [Commented] (HBASE-6740) Build out a toolset to make regular user operations on HBase tables
[ 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
[jira] [Commented] (HBASE-6740) Build out a toolset to make regular user operations on HBase tables
[ https://issues.apache.org/jira/browse/HBASE-6740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451054#comment-13451054 ] Amandeep Khurana commented on HBASE-6740: - Yup, separate maven module works too. > 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
[jira] [Commented] (HBASE-6740) Build out a toolset to make regular user operations on HBase tables
[ https://issues.apache.org/jira/browse/HBASE-6740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450995#comment-13450995 ] Andrew Purtell commented on HBASE-6740: --- Why not a separate Maven module? Why a separate repo? People aren't going to want tools shipped with HBase? > 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
[jira] [Commented] (HBASE-6740) Build out a toolset to make regular user operations on HBase tables
[ https://issues.apache.org/jira/browse/HBASE-6740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450861#comment-13450861 ] Amandeep Khurana commented on HBASE-6740: - Could very well be on Cloudera's public github for now, or could be a part of a separate package called hbase-tools in the current HBase repo. Access/commits don't necessarily have to be the same as they are for core at the moment. Do you have recommendations on where we could put them up? We don't necessarily have to get it right the first time. We can start with Cloudera's public repo and the code can be moved to some other repo if folks feel there's a more appropriate home. I really don't have a strong opinion on where it should be hosted. > 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
[jira] [Commented] (HBASE-6740) Build out a toolset to make regular user operations on HBase tables
[ https://issues.apache.org/jira/browse/HBASE-6740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450842#comment-13450842 ] stack commented on HBASE-6740: -- Sounds good (I like moving stuff out of core). How you see it working AK? What repo? Who'd have access? Etc. > 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
