[ 
https://issues.apache.org/jira/browse/MAPREDUCE-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13055700#comment-13055700
 ] 

Harsh J commented on MAPREDUCE-2293:
------------------------------------

To clarify, the " " (space) is the only real constraint per the implementation 
right now. The comma was the only thing I added in for sanity for subsequent 
jobs, since FileInputFormat uses plain paths and commas to handle path lists.

The restriction can surely be lifted away off the comma (,). The " " (space) 
dependency for MO configuration can be done away with too, but would require me 
to use a control or escape character as delimiter and base64 encoding (for xml 
to allow) which may complicate the code a bit and make it impossible to easily 
see the conf values. Is it agreed to restrict on " " and ","?

> Enhance MultipleOutputs to allow additional characters in the named output 
> name
> -------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-2293
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2293
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>    Affects Versions: 0.21.0
>            Reporter: David Rosenstrauch
>            Assignee: Harsh J
>            Priority: Minor
>             Fix For: 0.23.0
>
>         Attachments: mapreduce.mo.removecheck.r1.diff, 
> mapreduce.mo.removecheck.r2.diff
>
>
> Currently you are only allowed to use alpha-numeric characters in a named 
> output name in the MultipleOutputs class.  This is a bit of an onerous 
> restriction, as it would be extremely convenient to be able to use non 
> alpha-numerics in the name too.  (E.g., a '.' character would be very 
> helpful, so that you can use the named output name for holding a file 
> name/extension.  Perhaps '-' and a '_' characters as well.)
> The restriction seems to be somewhat arbitrary - it appears to be only 
> enforced in the checkTokenName method.  (Though I don't know if there's any 
> downstream impact by loosening this restriction.)
> Would be extremely helpful/useful to have this fixed though!

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to