Apache9 commented on pull request #1774: URL: https://github.com/apache/hbase/pull/1774#issuecomment-643058209
> `The point here is when do you want to do this? In normal single read/write path, we just need to locate a single region. And for scanning, we need to locate to the next region when the current region is done, or for reverse scan we need to locate to the previous region. We do not need to get the location of a region and then go to the next region.` > > This makes sense. > > A catalogjanitor or scp or hbck2 doing a visit to each row would not go via this interface. It would be done internal to the master (i guess). Oh, I haven't fully thought of these parts yet. They need to scan the whole root table, especially the catalogjanitor. But as you said they are at master side, so I guess it is OK, we could even expose the master local region directly to them. But maybe we need a RootTableAccessor then, for holding some common logic when accessing the root table. ---------------------------------------------------------------- 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]
