You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Kengo Seki (JIRA)" <ji...@apache.org> on 2015/05/09 16:08:00 UTC

[jira] [Resolved] (MAPREDUCE-3642) Remove hardcoded strings from the JC#displayTasks() call.

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

Kengo Seki resolved MAPREDUCE-3642.
-----------------------------------
          Resolution: Fixed
    Target Version/s:   (was: )

Closing because already fixed. Please reopen if I am wrong.

> Remove hardcoded strings from the JC#displayTasks() call.
> ---------------------------------------------------------
>
>                 Key: MAPREDUCE-3642
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3642
>             Project: Hadoop Map/Reduce
>          Issue Type: Sub-task
>          Components: client
>    Affects Versions: 2.0.0-alpha
>            Reporter: Harsh J
>              Labels: newbie
>         Attachments: MR-3642.1.patch
>
>
> This is to address Eli's comments on the parent task:
> bq. 1. The error messages should generate the lists of valid states and types from their definitions rather than hard-coding them into the error messages.
> bq. 2. Aren't these types and states defined somewhere already? Seems like they're a public API and therefore shouldn't have to duplicate the definition of them in taskTypes and taskStates.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)