hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suhas Gogate (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 16:37:45 GMT

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

Suhas Gogate commented on HADOOP-5582:
--------------------------------------

1. About converting to compact string and then using existing code is definitely a less change,
but may not be a right way to go. What if tomorrow the compact format gets deprecated? Also
as you mentioned we don't need to do extra conversion just to use existing code. 

2. Vaidya is a offline tool and uses the default job history parser to read and parse the
job history file. Although it presents all the counters as a key/value pairs in the format
or interface exposed by Vaidya tool for its rule writers. Thus it makes rules agnostic to
any changes in hadoop counters and their representation.

> 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