[ 
http://issues.apache.org/jira/browse/HADOOP-559?page=comments#action_12437888 ] 
            
Doug Cutting commented on HADOOP-559:
-------------------------------------

Overall, this looks great!

Why doesn't it work for local globs?  It's all implemented in the generic code, 
but, with an empty hadoop-site.xml (i.e., local fs), then 'bin/hadoop dfs -ls 
"conf/*.template"' shows zero results.  I'm mostly just curious.  It seems like 
it ought to work, but it doesn't (though that functionality isn't needed).

Also, you add some new public methods to FileSystem.java, listPaths(Path[]) and 
listPaths(Path[], PathFilter).  Do these really need to be public?  If so, they 
need better javadoc, explaining how they work.

Thanks!

> Support file patterns in dfs commands
> -------------------------------------
>
>                 Key: HADOOP-559
>                 URL: http://issues.apache.org/jira/browse/HADOOP-559
>             Project: Hadoop
>          Issue Type: New Feature
>          Components: dfs
>    Affects Versions: 0.6.2
>            Reporter: Hairong Kuang
>         Assigned To: Arun C Murthy
>             Fix For: 0.7.0
>
>         Attachments: glob.patch
>
>
> Currently DFSShell does not support file patterns in dfs file names. It's 
> quite inconvenient for users when they need to manipulate multiple files.
> This issue is intended to extend DFSShell to interprete file patterns. A file 
> pattern contains special special pattern matching characters:
> ?: matches any character
> *: matches zero or more characters
> [abc]: matches a character from character set {a, b, c}
> [a-c]: matches a character from character range: {a...c}
> [^a]: matches a character not in character set or range {a}
> \c:  escape any special meaning of character c
>  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to