hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (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 22:15:29 GMT

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

Alejandro Abdelnur commented on MAPREDUCE-2293:
-----------------------------------------------

David,

The current implementation uses '_' as separator for multi-named outputs, FIXNAME_VARNAME,
this means that the use of '_' as part of the FIXNAME or VARNAME would break things if you
allow '_'.

Allen,

Regarding allowing other characters, even if HDFS supports UTF, I'm not sure what will happen
if you have SPACEs and COMMAs in the names of a file and you use that file as an input for
a MR job. Will the InputFormat class take a file a 2 different PATHs?



Said this, allowing a reduced set of symbols would be possible.


> 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