From cc2babc1f75c93bf89a8f10da525f944c15d02ea Mon Sep 17 00:00:00 2001 From: Adam Antal Date: Thu, 4 Oct 2018 15:20:41 -0700 Subject: [PATCH] HDFS-13950. ACL documentation update to indicate that ACL entries are capped by 32. Contributed by Adam Antal. Signed-off-by: Wei-Chiu Chuang --- .../hadoop-hdfs/src/site/markdown/HdfsPermissionsGuide.md | 2 ++ 1 file changed, 2 insertions(+) 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 82b5cec09f..a4a3b7d5cb 100644 --- a/hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/HdfsPermissionsGuide.md +++ b/hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/HdfsPermissionsGuide.md @@ -221,6 +221,8 @@ Note that the copy occurs at time of creation of the new file or sub-directory. The default ACL must have all minimum required ACL entries, including the unnamed user (file owner), unnamed group (file group) and other entries. If the user doesn't supply one of these entries while setting a default ACL, then the entries are inserted automatically by copying the corresponding permissions from the access ACL, or permission bits if there is no access ACL. The default ACL also must have mask. As described above, if the mask is unspecified, then a mask is inserted automatically by calculating the union of permissions on all entries that would be filtered by the mask. +Note that you can not have unlimited amount of ACL entries for a given file or directory. The maximum number is 32 for access and 32 for default entries which is 64 in total. + When considering a file that has an ACL, the algorithm for permission checks changes to: * If the user name matches the owner of file, then the owner