[
https://issues.apache.org/jira/browse/MAPREDUCE-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12989931#comment-12989931
]
Allen Wittenauer commented on MAPREDUCE-2293:
---------------------------------------------
If InputFormats can't take a file with commas or spaces, then that's a bug with
InputFormat. Even so: that's not a reason to restrict the character set so
gratuitously. Just because a file is generated as output doesn't mean it is
going to be used for input for some other MR phase.
> 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 Chouraria
> Priority: Minor
> Attachments: mapreduce.mo.removecheck.r1.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
