You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Robert Chansler (JIRA)" <ji...@apache.org> on 2009/10/09 19:47:31 UTC

[jira] Updated: (HADOOP-5582) Hadoop Vaidya throws number format exception due to changes in the job history counters string format (escaped compact representation).

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

Robert Chansler updated HADOOP-5582:
------------------------------------

    Release Note:   (was: This patch fixes the number format exception causes due to change in job history counters string format.)

Editorial pass over all release notes prior to publication of 0.21. Bug.

> Hadoop Vaidya throws number format exception due to changes in the job history counters string format (escaped compact representation).
> ---------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-5582
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5582
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.20.0
>            Reporter: Suhas Gogate
>            Assignee: Suhas Gogate
>             Fix For: 0.21.0
>
>         Attachments: vaidya-0.21.0-5582-5764.patch, vaidya_patch_21.patch
>
>
> Hadoop Vaidya (contrib/vaidya) tool throws number format exception while parsing the job history log files due to change in the format of counters string in 0.20.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.