[
https://issues.apache.org/jira/browse/HADOOP-10112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Li updated HADOOP-10112:
--------------------------------
Attachment: HADOOP-10112.004.patch
Basically, the problem is that: when a wildcard is in the path, FileSystem
object splits the whole path into components, and then get matches/status of
each component. However, Har file root path doesn't start with "/" so it can't
process any prefix.
For example, the .har file is created at /user/me/foo.har.
When user does "hadoop dfs -ls har:///test/foo.har/* ", FileSystem object
passes each component path to HarFileSystem: /, /test, /test/foo.har,
/test/foo.har/*. HarFileSystem doesn't recognize any prefix pathes "/" or
"/test" since they are not in har file system.
The fix is to redirect the request to its source file system(e.g., HDFS) for
the prefix paths.
Uploaded a patch for branch 2.3.
> har file listing doesn't work with wild card
> ---------------------------------------------
>
> Key: HADOOP-10112
> URL: https://issues.apache.org/jira/browse/HADOOP-10112
> Project: Hadoop Common
> Issue Type: Bug
> Components: tools
> Affects Versions: 2.3.0
> Reporter: Brandon Li
> Assignee: Brandon Li
> Attachments: HADOOP-10112.004.patch
>
>
> [test@test001 root]$ hdfs dfs -ls har:///tmp/filename.har/*
> -ls: Can not create a Path from an empty string
> Usage: hadoop fs [generic options] -ls [-d] [-h] [-R] [<path> ...]
> It works without "*".
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
