xinglin opened a new pull request, #5071: URL: https://github.com/apache/hadoop/pull/5071
### Description of PR In RBF, trash files are moved to trash root under user's home dir at the corresponding namespace/namenode where the files reside. This was added in [HDFS-16024](https://issues.apache.org/jira/browse/HDFS-16024). When the user home dir is not created before-hand at a namenode, we run into permission denied exceptions when trying to create the parent dir for the trash file before moving the file into it. We propose to enhance Router, to auto-create a user home's dir at the namenode for trash paths, using router's identity (which is assumed to be a super-user). ### How was this patch tested? Add a new unit test (`testMoveToTrashAutoCreateUserHome`) to TestRouterTrash. mvn test -Dtest="TestRouterTrash" ``` [INFO] ------------------------------------------------------- [INFO] T E S T S [INFO] ------------------------------------------------------- [INFO] Running org.apache.hadoop.hdfs.server.federation.router.TestRouterTrash [INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.326 s - in org.apache.hadoop.hdfs.server.federation.router.TestRouterTrash [INFO] [INFO] Results: [INFO] [INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0 ``` ### For code changes: - [ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')? - [ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation? - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, `NOTICE-binary` files? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
