hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amareshwari Sriramadasu (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6006) pipes does not allow jobconf values containing commas
Date Mon, 15 Jun 2009 03:54:07 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-6006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719381#action_12719381

Amareshwari Sriramadasu commented on HADOOP-6006:

Christian, -jobConf option is deprecated from branch 0.19, and users are advised to use -D

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

View raw message