Return-Path: 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 36D9B10A4A for ; Sat, 7 Dec 2013 02:01:37 +0000 (UTC) Received: (qmail 51288 invoked by uid 500); 7 Dec 2013 02:01:37 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 51165 invoked by uid 500); 7 Dec 2013 02:01:37 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-issues@hadoop.apache.org Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 51156 invoked by uid 99); 7 Dec 2013 02:01:36 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 07 Dec 2013 02:01:36 +0000 Date: Sat, 7 Dec 2013 02:01:36 +0000 (UTC) From: "Chuan Liu (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (MAPREDUCE-5674) Missing start and finish time in mapred.JobStatus 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-5674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chuan Liu updated MAPREDUCE-5674: --------------------------------- Attachment: MAPREDUCE-5674.patch Attach a patch. > Missing start and finish time in mapred.JobStatus > ------------------------------------------------- > > Key: MAPREDUCE-5674 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-5674 > Project: Hadoop Map/Reduce > Issue Type: Bug > Affects Versions: 3.0.0 > Reporter: Chuan Liu > Assignee: Chuan Liu > Attachments: MAPREDUCE-5674.patch > > > The JobStatus obtained from the JobClient or runningJob has no start or finish time for the job -- the start and finish time is always 0. This is a regression with respect to 1.0 mapreduce client and JobStatus API. This can also lead to regressions in downstream projects. For example, we discovered the problem in webhcat that the jobstatus for mapreduce job submmited to webhcat always reports start time as 0. -- This message was sent by Atlassian JIRA (v6.1#6144)