Return-Path: 
 <hdfs-issues-return-133493-apmail-hadoop-hdfs-issues-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-hdfs-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 A8E8F181E2
	for <apmail-hadoop-hdfs-issues-archive@minotaur.apache.org>;
 Mon, 24 Aug 2015 05:13:46 +0000 (UTC)
Received: (qmail 37231 invoked by uid 500); 24 Aug 2015 05:13:46 -0000
Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org
Received: (qmail 37176 invoked by uid 500); 24 Aug 2015 05:13:46 -0000
Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:hdfs-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:hdfs-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:hdfs-issues@hadoop.apache.org>
List-Id: <hdfs-issues.hadoop.apache.org>
Reply-To: hdfs-issues@hadoop.apache.org
Delivered-To: mailing list hdfs-issues@hadoop.apache.org
Received: (qmail 37159 invoked by uid 99); 24 Aug 2015 05:13:46 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Aug 2015 05:13:46 +0000
Date: Mon, 24 Aug 2015 05:13:46 +0000 (UTC)
From: "Vinayakumar B (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12829474.1431500481000.142710.1440393226088@Atlassian.JIRA>
In-Reply-To: <JIRA.12829474.1431500481000@Atlassian.JIRA>
References: <JIRA.12829474.1431500481000@Atlassian.JIRA>
 <JIRA.12829474.1431500481913@arcas>
Subject: [jira] [Commented] (HDFS-8388) Time and Date format need to be in
 sync in Namenode UI page
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/HDFS-8388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14708784#comment-14708784 ] 

Vinayakumar B commented on HDFS-8388:
-------------------------------------

1. {code}     var HELPERS = {
       'helper_date_tostring' : function (chunk, ctx, bodies, params) {
         var value = dust.helpers.tap(params.value, chunk, ctx);
-        return chunk.write('' + new Date(Number(value)).toLocaleString());
+        return chunk.write('' + moment(Number(v)).format('ddd MMM DD HH:mm:ss ZZ YYYY'));
       }
     };{code}
Here, {{Number(v)}}, there is no {{v}}. You need to replace with {{value}}.

2. Need to fix 2 checkstyles out of 3 shown
3. You can clean lines with whitespace endings, though this can be done during commit.


In addition to the above changes, just remove duplicate line in {{dfshealth.html}}. Its not from this issue, but i think that also can go along with this patch.
{{</script><script type="text/javascript" src="/static/moment.min.js">}}

> Time and Date format need to be in sync in Namenode UI page
> -----------------------------------------------------------
>
>                 Key: HDFS-8388
>                 URL: https://issues.apache.org/jira/browse/HDFS-8388
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Archana T
>            Assignee: Surendra Singh Lilhore
>            Priority: Minor
>         Attachments: HDFS-8388-002.patch, HDFS-8388-003.patch, HDFS-8388-004.patch, HDFS-8388-005.patch, HDFS-8388.patch, HDFS-8388_1.patch, ScreenShot-InvalidDate.png
>
>
> In NameNode UI Page, Date and Time FORMAT  displayed on the page are not in sync currently.
> Started:Wed May 13 12:28:02 IST 2015
> Compiled:23 Apr 2015 12:22:59 
> Block Deletion Start Time   13 May 2015 12:28:02
> We can keep a common format in all the above places.



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