[
https://issues.apache.org/jira/browse/TEZ-3712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16005420#comment-16005420
]
Kuhu Shukla commented on TEZ-3712:
----------------------------------
Did some more analysis as to why we see discrepancy in the output of
LocalFIleSystem.delete() versus LocalFSFileContext.delete().
FileContext sets permissions using a new Configuration object that reads
"fs.permissions.umask-mode" from core-site.xml. This logic is not present in
the case of LocalFileSystem.
The current patch would address this issue similar to how NM does in its
deletion service. [~jeagles], appreciate your thoughts on the above finding and
the patch. Thanks a lot!
> Use Local FileContext for deleting dag level directories
> --------------------------------------------------------
>
> Key: TEZ-3712
> URL: https://issues.apache.org/jira/browse/TEZ-3712
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Kuhu Shukla
> Assignee: Kuhu Shukla
> Attachments: TEZ-3712.001.patch
>
>
> To delete dag level directories that are not empty, use FileContext utilities
> instead of LocalFileSystem. This is since the LocalFileSystem call boils down
> to File.io delete call which does not work for non-empty directories.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
