You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Christian Kunz (JIRA)" <ji...@apache.org> on 2009/06/12 22:39:08 UTC

[jira] Updated: (HADOOP-6006) pipes does not allow jobconf values containing commas

     [ https://issues.apache.org/jira/browse/HADOOP-6006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Kunz updated HADOOP-6006:
-----------------------------------

    Fix Version/s: 0.18.4
         Assignee: Christian Kunz
           Status: Patch Available  (was: Open)

> 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
>
>
> 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.