Return-Path: 
 <mapreduce-issues-return-77416-apmail-hadoop-mapreduce-issues-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 52D7217302
	for <apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org>;
 Thu, 16 Apr 2015 17:09:59 +0000 (UTC)
Received: (qmail 55798 invoked by uid 500); 16 Apr 2015 17:09:59 -0000
Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org
Received: (qmail 55741 invoked by uid 500); 16 Apr 2015 17:09:59 -0000
Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:mapreduce-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:mapreduce-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:mapreduce-issues@hadoop.apache.org>
List-Id: <mapreduce-issues.hadoop.apache.org>
Reply-To: mapreduce-issues@hadoop.apache.org
Delivered-To: mailing list mapreduce-issues@hadoop.apache.org
Received: (qmail 55730 invoked by uid 99); 16 Apr 2015 17:09:59 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Apr 2015 17:09:59 +0000
Date: Thu, 16 Apr 2015 17:09:59 +0000 (UTC)
From: "Siqi Li (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <JIRA.12821559.1429199427000.20486.1429204198999@Atlassian.JIRA>
In-Reply-To: <JIRA.12821559.1429199427000@Atlassian.JIRA>
References: <JIRA.12821559.1429199427000@Atlassian.JIRA>
 <JIRA.12821559.1429199427820@arcas>
Subject: [jira] [Commented] (MAPREDUCE-6319) Get rid of the usage of
 parseHadoopAttemptID in HsTaskPage for consistency
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


    [ 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
(v6.3.4#6332)