hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-2293) Enhance MultipleOutputs to allow additional characters in the named output name
Date Wed, 02 Feb 2011 21:02:28 GMT

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

Allen Wittenauer commented on MAPREDUCE-2293:
---------------------------------------------

It would be very useful to have the HDFS folks chime in... my understanding is that HDFS is
essentially UTF-16 by virtue of using java String everywhere.  So it makes complete sense
to only block the character /. 

I'm curious as to why the NULL character causes issues.

If users want to shoot themselves in the foot by naming things inconsistently, that isn't
our place to get in their way.

> 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

        

Mime
View raw message