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:38:46 GMT

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

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

>From what I understand, you could something like 
{code}
Counters c = Counters.fromEscapedCompactString(counterString);
String compactString = c.toCompactStrihng();
// do what you do currently .. but with compactString and not counterString
Matcher m = _pattern.matcher(counters);
while(m.find()){
  String ctuple = m.group(0);
  //String ctuple = c1tuple.substring(0, c1tuple.length()-1);
....
...
.
{code}

This might not be efficient but will will reduce code change and testing time. So basically
what you will be doing here is you will convert the new format to old format and pass to the
code.

----

Few questions :
# Seems like there is a parser written here for job history. Why cant you use the existing
job history parser?
# Seems like counters are maintained as key val pair. Why can a global counter be used and
all new counter can simply be added to it?

I have not seen the whole code. These questions are based on the impression that I am getting
looking at the patch.

> 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