HBASE-11481 TableSnapshotInputFormat javadoc wrongly claims HBase 'enforces security'
This commit is contained in:
parent
ed9ab70180
commit
f0b9b6bbf2
|
@ -74,9 +74,8 @@ import com.google.common.annotations.VisibleForTesting;
|
||||||
* from each RecordReader. An internal RegionScanner is used to execute the {@link Scan} obtained
|
* from each RecordReader. An internal RegionScanner is used to execute the {@link Scan} obtained
|
||||||
* from the user.
|
* from the user.
|
||||||
* <p>
|
* <p>
|
||||||
* HBase owns all the data and snapshot files on the filesystem. Only the HBase user can read from
|
* HBase owns all the data and snapshot files on the filesystem. Only the 'hbase' user can read from
|
||||||
* snapshot files and data files. HBase also enforces security because all the requests are handled
|
* snapshot files and data files.
|
||||||
* by the server layer, and the user cannot read from the data files directly.
|
|
||||||
* To read from snapshot files directly from the file system, the user who is running the MR job
|
* To read from snapshot files directly from the file system, the user who is running the MR job
|
||||||
* must have sufficient permissions to access snapshot and reference files.
|
* must have sufficient permissions to access snapshot and reference files.
|
||||||
* This means that to run mapreduce over snapshot files, the MR job has to be run as the HBase
|
* This means that to run mapreduce over snapshot files, the MR job has to be run as the HBase
|
||||||
|
|
Loading…
Reference in New Issue