hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-2293) Enhance MultipleOutputs to allow additional characters in the named output name
Date Thu, 05 Feb 2015 17:30:37 GMT

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

Hadoop QA commented on MAPREDUCE-2293:
--------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12555681/mapreduce.mo.removecheck.r5.diff
  against trunk revision afbecbb.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5157//console

This message is automatically generated.

> 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
>         Attachments: mapreduce.mo.removecheck.r1.diff, mapreduce.mo.removecheck.r2.diff,
mapreduce.mo.removecheck.r3.diff, mapreduce.mo.removecheck.r4.diff, mapreduce.mo.removecheck.r5.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 was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message