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 "Brahma Reddy Battula (JIRA)" <ji...@apache.org> on 2015/04/16 18:28:58 UTC

[jira] [Assigned] (MAPREDUCE-6319) Get rid of the usage of parseHadoopAttemptID in HsTaskPage for consistency

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

Brahma Reddy Battula reassigned MAPREDUCE-6319:
-----------------------------------------------

    Assignee: Brahma Reddy Battula

> Get rid of the usage of parseHadoopAttemptID in HsTaskPage for consistency
> --------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-6319
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6319
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: webapps
>            Reporter: Akira AJISAKA
>            Assignee: Brahma Reddy Battula
>            Priority: Minor
>
> Per [~jira.shegalov]'s comment in MAPREDUCE-6300:
> parseHadoopAttemptID function in yarn.plugin.dt.js is used only by HsTaskPage for sorting MapReduce attempt id by numerical. On the other hand, others are calling parseHadoopID function for sorting various ids (including MapReduce attempt id) by string. We can get rid of parseHadoopAttemptID and replace with parseHadoopID for consistency.



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