hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gera Shegalov (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 19:06:59 GMT

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

Gera Shegalov updated MAPREDUCE-6319:
-------------------------------------
    Status: Open  (was: Patch Available)

This patch is not sufficient.

Check the code in HsTaskPage:
{code}
        int sortId = attempt.getID().getId()
                   + (attempt.getID().getTaskId().getId() * 10000);

        attemptsTableData.append("[\"")
        .append(sortId + " ").append(taid).append("\",\"")
        .append(ta.getState()).append("\",\"")
{code}

It should output only {{taid}}

> 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