HDFS permissions control who can read, write, or traverse files in the namespace. Permission changes should target the smallest path that supports the job or tenant workflow, because recursive changes can expose data or block running jobs.
The filesystem shell uses chmod, chgrp, and chown with Unix-like permission bits. The caller must own the path or have superuser rights for ownership changes.
Object stores reached through Hadoop can ignore or reject Unix-style permission commands. Use this procedure for HDFS paths, not for S3A or other object-store URIs.
Related: How to upload a file to HDFS
Related: How to enable Kerberos for Hadoop
$ hdfs dfs -ls /data/events drwxr-x--- - alice analytics 0 2026-06-17 03:20 /data/events
$ hdfs dfs -chmod 750 /data/events
$ hdfs dfs -chgrp analytics /data/events
$ hdfs dfs -chmod -R 750 /data/events/restricted
Recursive permission changes affect every file below the path and can break jobs that depend on broader read access.
$ hdfs dfs -ls /data drwxr-x--- - alice analytics 0 2026-06-17 03:22 /data/events
$ hdfs dfs -test -r /data/events