Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
HADOOP-6421 added symbolic links to FileContext. Resolving symlinks is done on the client-side, and therefore requires client support. An HDFS symlink (created by FileContext) when accessed by FileSystem will result in an unhandled UnresolvedLinkException. Because not all users will migrate from FileSystem to FileContext in lock step, and we want users of FileSystem to be able to access all paths created by FileContext, we need to support symlink resolution in FileSystem as well, to facilitate migration to FileContext.
Attachments
Attachments
Issue Links
- is blocked by
-
HADOOP-9370 Write FSWrapper class to wrap FileSystem and FileContext for better test coverage
- Resolved
- is depended upon by
-
HADOOP-9758 Provide configuration option for FileSystem/FileContext symlink resolution
- Closed
- is duplicated by
-
HDFS-4561 Symlinks broken in DFS
- Closed
-
HADOOP-7905 Port FileContext symlinks to FileSystem
- Resolved
- is related to
-
HDFS-4205 fsck fails with symlinks
- Closed
-
HADOOP-7905 Port FileContext symlinks to FileSystem
- Resolved
-
HADOOP-9652 Allow RawLocalFs#getFileLinkStatus to fill in the link owner and mode if requested
- Closed
- is required by
-
HDFS-4933 add symlink support to WebHDFS to HTTP REST API & client filesystem
- Open
-
HDFS-4934 add symlink support to WebHDFS server side
- Open
-
HDFS-4935 add symlink support to HttpFS server side
- Resolved
- relates to
-
HADOOP-8195 Backport FileContext to branch-1
- Resolved