hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siqi Li (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-6319) Get rid of the usage of parseHadoopAttemptID in HsTaskPage for consistency
Date Thu, 16 Apr 2015 17:09:59 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-6319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14498314#comment-14498314

Siqi Li commented on MAPREDUCE-6319:

You cannot just use parseHadoopID method for attemptID, because they have different format.
for AttemptID, it is a formatted like "20000 attempt_1360183373897_0001_m_000002_0",
whereas parseHadoopID method is trying to parse something like
 "<a href='app/application_1360183373897_0001'>application_1360183373897_0001"

In MAPREDUCE-6316, I have added anchor tag for AttemptID, maybe we can also remove the integer
before the attemptID and then we can use parseHadoopID method

> 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

View raw message