Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
In the current symbolic link code an exception is thrown from the NameNode to FileContext for every symbolic link in a path. As an optimization to remove these round trips the NameNode can resolve symbolic links that have relative or absolute targets internally without going up to FileContext. Partially and fully qualified link targets still need to get resolved by FileContext since they may refer to different file systems.
Attachments
Issue Links
- depends upon
-
HDFS-245 Create symbolic links in HDFS
- Closed