Apache9 commented on pull request #2552: URL: https://github.com/apache/hbase/pull/2552#issuecomment-709941231
Moving tools to hbase-tool means we can not use the tool in hbase-server module any more, what if later we find out that we need to use this tool in hbase-server? What's the plan? And what is the plan for hbase-mapreduce module? We want to make it depend on hbase-tool on make hbase-tool depend on it or they are completely no relationship? Have you written down the plan? And what is the plan for the shaded module? We used to have a hbase-shaded-server, and once we created the hbase-mapreduce module, we changed the shaded module to hbase-shaded-mapreduce. So what is the plan for this new hbase-tool module? Have you written it down somewhere? Why not write a design doc before writing the code? You just do what you want, without telling others your 'plan'. I just asked about what is the scope of the new module, then you put up a bunch of changes without design doc, without consensus? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
