Description
This means that they can't write/read from files that the yarn user doesn't have permissions to but the submitting user does. I don't think this isn't a problem when running with Hadoop security, because the executor processes will be run as the submitting user.
Attachments
Issue Links
- causes
-
SPARK-31551 createSparkUser lost user's non-Hadoop credentials
- Resolved
- links to