[HDFS-7508] Clean up path resolving in FSNamesystem/FSDirectory

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: namenode
• Assignee: Jing Zhao
• Reporter: Jing Zhao
• Created: 11/Dec/14 03:04
• Updated: 06/Jan/17 22:04

Description

There are several issues with our current path resolving process:

1. For a single operation we may repeat resolving the same path
2. Each operation needs to invoke multiple calls for path resolving, including handling reserved path, breaking the path into components, identifying corresponding inodes etc. This makes the path resolving process hard to follow.
3. The logic in INodesInPath is complicated and not direct.

Ideally for each operation we should only resolve the path once in the beginning, and always use the INodesInPath instance afterwards. This requires a lot of code cleanup. We will use this jira as the umbrella jira to track all the efforts.

Sub-Tasks

• Avoid resolving path in FSPermissionChecker: Closed
• Simplify the logic in INodesInPath: Closed
• Avoid resolving path multiple times: Closed
• Avoid path resolution when getting FileStatus for audit logs: Closed
• Minor followon cleanups from HDFS-7543: Patch Available