[HDFS-7474] Avoid resolving path in FSPermissionChecker

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.7.0
• Component/s: namenode
• Target Version/s: 2.7.0
• Hadoop Flags: Reviewed
• Assignee: Jing Zhao
• Reporter: Jing Zhao
• Created: 04/Dec/14 22:40
• Updated: 10/Apr/15 20:29
• Resolved: 05/Dec/14 22:23

Description

Currently for an typical namenode operation a path can be resolved multiple times. Usually the FSPermissionChecker first takes the path string as input and resolve the path before the real checking. After permission checking the path is then resolved again (and again) for real operations in FSNamesystem and FSDirectory. Ideally we should resolve the path only once, and use INodesInPath internally afterwards. As a first step, we can start from avoiding path resolving in FSPermissionChecker.

Issue Links

• is related to: HDFS-6585 INodesInPath.resolve is called multiple times in FSNamesystem.setPermission