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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.20.0
• Fix Version/s: 0.21.0
• Hadoop Flags: Reviewed
• Release Note: Fixed error parsing job history counters after change of counter format.
• Assignee: Suhas
• Reporter: Suhas
• Created: 26/Mar/09 16:20
• Updated: 02/May/13 02:29
• Resolved: 16/May/09 16:14

Description

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.

Issue Links

• is depended upon by: HADOOP-5764 Hadoop Vaidya test rule (ReadingHDFSFilesAsSideEffect) fails w/ exception if number of map input bytes for a job is zero.
• relates to: HADOOP-5583 method fromEscapedCompactString() from the depricated class, org.apache.hadoop.mapred.Counters is not supported in org.apache.hadoop.mapreduce.Counters