hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brahma Reddy Battula (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-6319) Get rid of the usage of parseHadoopAttemptID in HsTaskPage for consistency
Date Thu, 16 Apr 2015 16:41:00 GMT

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

Brahma Reddy Battula updated MAPREDUCE-6319:
--------------------------------------------
    Attachment: MAPREDUCE-6319.patch

> 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
>         Attachments: MAPREDUCE-6319.patch
>
>
> 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)

Mime
View raw message