[HADOOP-10019] make symlinks production-ready

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.3.0
• Component/s: fs
• Assignee: Ajith S
• Reporter: Colin McCabe
• Created: 04/Oct/13 01:56
• Updated: 10/Nov/16 20:10

Description

This is an umbrella JIRA for all the things we have to do to make symlinks production-ready for Hadoop 2.3.

Note that some of these subtasks are scheduled for 2.1.2 / 2.2, but the overall effort is for 2.3.

Issue Links

• is related to: HDFS-4559 WebHDFS does not allow resolution of Symlinks
• is related to: HDFS-5294 DistributedFileSystem#getFileLinkStatus should not fully qualify the link target
• is related to: HDFS-5303 A symlink within a snapshot pointing to a target outside the snapshot root can cause the snapshot contents to appear to change.
• is related to: HDFS-4935 add symlink support to HttpFS server side
• is related to: HDFS-5293 Symlink resolution requires unnecessary RPCs

Sub-Tasks

• FileSystem#globStatus and FileSystem#listStatus should resolve symlinks by default: Open
• isSymlink returns false for link to non-existing file: Open
• Add symlinks tests to TestFcLocalFsPermission: Open
• Filesystem and FileContext methods that follow symlinks should return unresolved paths: Open
• FileSystem#rename is broken, deletes target when renaming link to itself: Open
• Symlink resolution is fundamentally broken for multi-layered filesystems: Open
• new APIs for listStatus and globStatus to deal with symlinks: Open
• add distCp support for symlinks: Open
• Using backtick "`" as delimiter for parsing file path disallows "`" in file path name: Open
• listLocatedStatus does not support cross-filesystem symlinks: Open