Mailing-List: contact dev-help@sqoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@sqoop.apache.org
Date: Wed, 21 Nov 2012 05:23:59 +0000 (UTC)
From: "Jarek Jarcec Cecho (JIRA)" <jira@apache.org>
To: dev@sqoop.apache.org
Message-ID: <1085720461.10663.1353475439117.JavaMail.jiratomcat@arcas>
In-Reply-To: <1293365330.63422.1351897812157.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (SQOOP-673) Mapreduce submission manager should
 not call update() on finished submissions
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jarek Jarcec Cecho updated SQOOP-673:
-------------------------------------

    Attachment: SQOOP-673.patch
    
> Mapreduce submission manager should not call update() on finished submissions
> -----------------------------------------------------------------------------
>
>                 Key: SQOOP-673
>                 URL: https://issues.apache.org/jira/browse/SQOOP-673
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Jarek Jarcec Cecho
>             Fix For: 2.0.0
>
>         Attachments: SQOOP-673.patch
>
>
> Calling update() on finished submissions is not going to provide any updates. Also calling update() might actually hurt Sqoop as remote job tracker might be rebooted in the meantime and thus changing perfectly fine statistics to UNKNOWN state.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira