[
http://issues.apache.org/jira/browse/HADOOP-619?page=comments#action_12455550 ]
Runping Qi commented on HADOOP-619:
-----------------------------------
How flexible is globPaths()?
Is p.glovPaths() legal for the following p:
p = "root1/*/foo/*/*.gz"
p = "root2/*/200611??/*/*.gz"
In other words, can I specify the following inut paths:
"root1/*/foo/*/*.gz,root2/*/200611??/*/*.gz" in jobconf?
I am OK with Owen's proposal.
Another point related to specifying different mapper classes for different
input files: we should
use some similar syntax:
"[EMAIL PROTECTED]/*/foo/*/*.gz,[EMAIL PROTECTED]/*/200611??/*/*.gz"
thoughts?
> Unify Map-Reduce and Streaming to take the same globbed input specification
> ---------------------------------------------------------------------------
>
> Key: HADOOP-619
> URL: http://issues.apache.org/jira/browse/HADOOP-619
> Project: Hadoop
> Issue Type: Improvement
> Components: mapred
> Reporter: eric baldeschwieler
> Assigned To: Sanjay Dahiya
>
> Right now streaming input is specified very differently from other map-reduce
> input. It would be good if these two apps could take much more similar input
> specs.
> In particular -input in streaming expects a file or glob pattern while MR
> takes a directory. It would be cool if both could take a glob patern of
> files and if both took a directory by default (with some patern excluded to
> allow logs, metadata and other framework output to be safely stored).
> We want to be sure that MR input is backward compatible over this change. I
> propose that a single file should be accepted as an input or a single
> directory. Globs should only match directories if the paterns is '/'
> terminated, to avoid massive inputs specified by mistake.
> Thoughts?
--
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
