[
https://issues.apache.org/jira/browse/HADOOP-6006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720282#action_12720282
]
Hadoop QA commented on HADOOP-6006:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12410510/patch.HADOOP-6006.0.18
against trunk revision 785065.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no tests are needed for this patch.
-1 patch. The patch command could not apply the patch.
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/505/console
This message is automatically generated.
> pipes does not allow jobconf values containing commas
> -----------------------------------------------------
>
> Key: HADOOP-6006
> URL: https://issues.apache.org/jira/browse/HADOOP-6006
> Project: Hadoop Core
> Issue Type: Bug
> Components: pipes
> Affects Versions: 0.18.3
> Reporter: Christian Kunz
> Assignee: Christian Kunz
> Fix For: 0.18.4
>
> 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.
