hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amar Kamat (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5582) Hadoop Vaidya throws number format exception due to changes in the job history counters string format (escaped compact representation).
Date Tue, 12 May 2009 11:23:45 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708401#action_12708401
] 

Amar Kamat commented on HADOOP-5582:
------------------------------------

Checked the code change related to {{Counters}}. Looks fine to me and seems like a right direction
(i.e counter string obtained from jobhistory should be decoded using {{Counters}}).
+1.

> 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 Core
>          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.


Mime
View raw message