My Oracle Support Banner

HDFS-6962: When Creating Directories In HDFS With Default ACLs, The Sub-directories Are Not Following POSIX Conventions (Doc ID 2054214.1)

Last updated on DECEMBER 19, 2019

Applies to:

Big Data Appliance Integrated Software - Version 4.2.0 and later
Generic (Platform Independent)

Symptoms

NOTE: In the examples that follow, user details, cluster names, hostnames, directory paths, filenames, etc. represent a fictitious sample (and are used to provide an illustrative example only). Any similarity to actual persons, or entities, living or dead, is purely coincidental and not intended in any manner. 

HDFS ACLs are including umask when calculating new ACL directories. With default ACLs defined, the sub-directory or files within the directory are not getting set with the expected permissions.

For example:


Running as user test, belonging to group test, on a directory owned by hdfs:hdfs with default ACLs defined:

 

$ id testuid=1004(test) gid=1005(test) groups=1005(test)
$ hadoop fs -getfacl /user/test/data
# file: /user/test/data
# owner: hdfs
# group: hdfs
user::rwx
user:hive:rwx
group::rwx
group:test:rwx
mask::rwx
other::r-x
default:user::rwx
default:user:hive:rwx
default:group::rwx
default:group:test:rwx
default:mask::rwx
default:other::r-x

With the current umask property configured for the HDFS client (gateway) in /etc/hadoop/conf/hdfs-site.xml:  


Effective permissions are incorrect with "r-x" due to mask being set "r-x"

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.