Apache9 commented on pull request #1774: URL: https://github.com/apache/hbase/pull/1774#issuecomment-643056999
> Trying to discuss to understand what is here, the direction, and to avoid having to do this explicitly. We have loads of experience in this area. The answer to suggestions or concerns can't be "...You can implement what you want in follow on issues, it is not a blocker problem here?" The current situation is that, I do not implement this stuff in this patch yet... Now in this patch, I just go to the active master to ask for the location of root table directly in AsyncMetaTableRegionLocator, this is the fastest way to make the code work and make progress here. As I've written in the design doc, we should do things step by step. The above discussions are for HBASE-24459, that's a follow on issue. If you want to implement the full RegionLocator for ConnectionRegistry just go ahead, I will challenge the implementation if I think there are better choices. But if you could make things work I'm also fine, as I said above, this is internal, we can change it later. Let's focus on the problems of this issue please? Stop shooting on air without any actual code... Thanks. ---------------------------------------------------------------- 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]
