Repository: hbase Updated Branches: refs/heads/master 82bb37070 -> 8ed4ee222
HBASE-12003 Fix SecureBulkLoadEndpoint class javadoc formatting Project: http://git-wip-us.apache.org/repos/asf/hbase/repo Commit: http://git-wip-us.apache.org/repos/asf/hbase/commit/8ed4ee22 Tree: http://git-wip-us.apache.org/repos/asf/hbase/tree/8ed4ee22 Diff: http://git-wip-us.apache.org/repos/asf/hbase/diff/8ed4ee22 Branch: refs/heads/master Commit: 8ed4ee222519a98f6e697c6a138a0e8fae4070f6 Parents: 82bb370 Author: Nick Dimiduk <[email protected]> Authored: Wed Sep 17 10:59:15 2014 -0400 Committer: Nick Dimiduk <[email protected]> Committed: Mon Sep 29 13:14:09 2014 -0700 ---------------------------------------------------------------------- .../security/access/SecureBulkLoadEndpoint.java | 29 ++++++++++---------- 1 file changed, 15 insertions(+), 14 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/hbase/blob/8ed4ee22/hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/SecureBulkLoadEndpoint.java ---------------------------------------------------------------------- diff --git a/hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/SecureBulkLoadEndpoint.java b/hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/SecureBulkLoadEndpoint.java index 2f04799..dfd71fc 100644 --- a/hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/SecureBulkLoadEndpoint.java +++ b/hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/SecureBulkLoadEndpoint.java @@ -73,22 +73,23 @@ import java.util.List; * security in HBase. * * This service addresses two issues: - * - * 1. Moving files in a secure filesystem wherein the HBase Client - * and HBase Server are different filesystem users. - * 2. Does moving in a secure manner. Assuming that the filesystem - * is POSIX compliant. + * <ol> + * <li>Moving files in a secure filesystem wherein the HBase Client + * and HBase Server are different filesystem users.</li> + * <li>Does moving in a secure manner. Assuming that the filesystem + * is POSIX compliant.</li> + * </ol> * * The algorithm is as follows: - * - * 1. Create an hbase owned staging directory which is - * world traversable (711): /hbase/staging - * 2. A user writes out data to his secure output directory: /user/foo/data - * 3. A call is made to hbase to create a secret staging directory - * which globally rwx (777): /user/staging/averylongandrandomdirectoryname - * 4. The user moves the data into the random staging directory, - * then calls bulkLoadHFiles() - * + * <ol> + * <li>Create an hbase owned staging directory which is + * world traversable (711): {@code /hbase/staging}</li> + * <li>A user writes out data to his secure output directory: {@code /user/foo/data}</li> + * <li>A call is made to hbase to create a secret staging directory + * which globally rwx (777): {@code /user/staging/averylongandrandomdirectoryname}</li> + * <li>The user moves the data into the random staging directory, + * then calls bulkLoadHFiles()</li> + * </ol> * Like delegation tokens the strength of the security lies in the length * and randomness of the secret directory. *
