Heya, I see that we maintain backreferences for hfilelinks. This appears to be used by HFileLinkCleaner to determine when an HFile has no HFileLinks and thus whether it can be deleted without orphaning those links.
This is problematic for using the mapreduce over snapshot files feature. However, restoring a snapshot can create HFileLinks to existing files in the restore directory. Those links then create back-references to the root path. Thus we have a situation where the user running the MR job requires write access to the hbase root path. Was this already discussed in the original ticket (HBASE-8369)? We mention the requirement of read permissions (and bypassing security) in the release note, but I didn't note any comments for write. Requiring write permission effectively means you can only MR as the hbase user, which is pretty much a non-starter for any interesting integration of feature. Thoughts? Thanks, Nick
