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 "Tsuyoshi OZAWA (JIRA)" <ji...@apache.org> on 2012/06/21 00:11:43 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13397935#comment-13397935 ] 

Tsuyoshi OZAWA commented on MAPREDUCE-3642:
-------------------------------------------

Harsh, 

I'd like to deal with this ticket, however, I don't have a contributor privilege.
Could you give it to me?

                
> 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: 0.24.0
>            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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira