[
https://issues.apache.org/jira/browse/MAPREDUCE-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Douglas updated MAPREDUCE-385:
------------------------------------
Status: Open (was: Patch Available)
{quote}
Okay, this makes the patch for the trunk out-dated.
Is there a chance for a hadoop-0.18.4 release? Then it would be nice if the
submitted patch could be added
{quote}
Unfortunately, neither patch applies to an active branch. There could be an
0.18.4 release if someone elects to [create
one|http://wiki.apache.org/hadoop/HowToRelease]. There are a handful of
important, unreleased
[changes|https://issues.apache.org/jira/browse/HADOOP/fixforversion/12313628]
committed to that branch, but nobody has rolled an official release.
This probably doesn't qualify as a blocking bug for 0.18 unless it used to work
in a previous release.
> pipes does not allow jobconf values containing commas
> -----------------------------------------------------
>
> Key: MAPREDUCE-385
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-385
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Christian Kunz
> Assignee: Christian Kunz
> Attachments: patch.HADOOP-6006, patch.HADOOP-6006.0.18
>
>
> Currently hadoop pipes does not allow a
> -jobconf <key>=<value>,<key>=<value>...
> commandline parameter with one or more commas in one of the values of the
> key-value pairs.
> One use case is key=mapred.join.expr, where the value is required to have
> commas.
> And it is not always convenient to add this to a configuration file.
> Submitter.java could easily be changed to check for backslash in front of a
> comma before using it as a delimiter.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
