Grokbase › Groups › Hadoop › common-dev › June 2009
FAQ
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


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.

Search Discussions

  • Christian Kunz (JIRA) at Jun 12, 2009 at 8:39 pm ⇧
    [ 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.
  • Christian Kunz (JIRA) at Jun 12, 2009 at 8:41 pm ⇧
    [ https://issues.apache.org/jira/browse/HADOOP-6006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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

    Status: Open (was: Patch Available)
    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.
  • Christian Kunz (JIRA) at Jun 12, 2009 at 8:43 pm ⇧
    [ https://issues.apache.org/jira/browse/HADOOP-6006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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

    Attachment: patch.HADOOP-6006.0.18
    patch.HADOOP-6006
    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.
  • Christian Kunz (JIRA) at Jun 12, 2009 at 8:45 pm ⇧
    [ https://issues.apache.org/jira/browse/HADOOP-6006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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

    Status: Patch Available (was: Open)

    Uploaded a couple of patches, one intended for hadoop-0.18, which includes changes to produce proper exit code when called from a unix command line.
    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.
  • Amareshwari Sriramadasu (JIRA) at Jun 15, 2009 at 3:54 am ⇧
    [ 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 instead.
    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.
  • Christian Kunz (JIRA) at Jun 15, 2009 at 4:26 am ⇧
    [ https://issues.apache.org/jira/browse/HADOOP-6006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719394#action_12719394 ]

    Christian Kunz commented on HADOOP-6006:
    ----------------------------------------

    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 (it also ensures proper exit code of pipes jobs in case of failure, see HADOOP-6030).
    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.
  • Hadoop QA (JIRA) at Jun 16, 2009 at 6:50 pm ⇧
    [ 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.
  • Christian Kunz (JIRA) at Jun 18, 2009 at 7:52 pm ⇧
    [ https://issues.apache.org/jira/browse/HADOOP-6006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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

    Attachment: (was: patch.HADOOP-6006)
    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.
  • Christian Kunz (JIRA) at Jun 18, 2009 at 7:52 pm ⇧
    [ https://issues.apache.org/jira/browse/HADOOP-6006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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

    Status: Open (was: Patch Available)
    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.
  • Christian Kunz (JIRA) at Jun 18, 2009 at 7:52 pm ⇧
    [ https://issues.apache.org/jira/browse/HADOOP-6006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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

    Attachment: patch.HADOOP-6006
    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.
  • Christian Kunz (JIRA) at Jun 18, 2009 at 7:54 pm ⇧
    [ https://issues.apache.org/jira/browse/HADOOP-6006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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

    Status: Patch Available (was: Open)

    Reversing order of file attachments for Hadoop QA
    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.
  • Hadoop QA (JIRA) at Jun 20, 2009 at 12:56 am ⇧
    [ https://issues.apache.org/jira/browse/HADOOP-6006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12722106#action_12722106 ]

    Hadoop QA commented on HADOOP-6006:
    -----------------------------------

    -1 overall. Here are the results of testing the latest attachment
    http://issues.apache.org/jira/secure/attachment/12411130/patch.HADOOP-6006
    against trunk revision 786278.

    +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 javadoc. The javadoc tool did not generate any warning messages.

    +1 javac. The applied patch does not increase the total number of javac compiler warnings.

    +1 findbugs. The patch does not introduce any new Findbugs warnings.

    +1 Eclipse classpath. The patch retains Eclipse classpath integrity.

    +1 release audit. The applied patch does not increase the total number of release audit warnings.

    +1 core tests. The patch passed core unit tests.

    -1 contrib tests. The patch failed contrib unit tests.

    Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/536/testReport/
    Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/536/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
    Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/536/artifact/trunk/build/test/checkstyle-errors.html
    Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/536/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.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupcommon-dev @
categorieshadoop
postedJun 10, '09 at 1:25a
activeJun 20, '09 at 12:56a
posts13
users1
websitehadoop.apache.org...
irc#hadoop

1 user in discussion

Hadoop QA (JIRA): 13 posts

Content

People

Support

Translate

site design / logo © 2022 Grokbase