From 094bc727c5d663d7635e2e1e40b1f28f63bbf64f Mon Sep 17 00:00:00 2001 From: Masatake Iwasaki Date: Sun, 22 May 2016 16:53:30 +0900 Subject: [PATCH] HDFS-10439. Update setOwner doc in HdfsPermissionsGuide. Contributed by John Zhuge. (cherry picked from commit 12eb5a7b11c36df5a57a3894a3a44bf47f47b954) --- .../hadoop-hdfs/src/site/markdown/HdfsPermissionsGuide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/HdfsPermissionsGuide.md b/hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/HdfsPermissionsGuide.md index 58b64a15a3d..ba027ac02e8 100644 --- a/hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/HdfsPermissionsGuide.md +++ b/hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/HdfsPermissionsGuide.md @@ -131,7 +131,7 @@ truncate | NO | N/A | N/A | WRIT [2] Any operation that checks WRITE permission on the parent directory also checks ownership if the [sticky bit](#Overview) is set. -[3] Calling `setOwner` to change the user that owns a file requires [HDFS super-user](#The_Super-User) access. HDFS super-user access is not required to change the group, but the caller must be a member of the specified group. +[3] Calling `setOwner` to change the user that owns a file requires [HDFS super-user](#The_Super-User) access. HDFS super-user access is not required to change the group, but the caller must be the owner of the file and a member of the specified group. Understanding the Implementation --------------------------------