hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5834) Job History log file format is not friendly for external tools.
Date Wed, 20 May 2009 19:01:46 GMT

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

Owen O'Malley commented on HADOOP-5834:
---------------------------------------

I think we should completely redesign the format. I'd propose using JSON so that it is trivial
to parse in python, perl and java. If we only put in newlines, between records all of the
needs are met using a standard layout. Furthermore, we can encode counters simply and directly
rather than complicated nested encoding schemes.

> Job History log file format is not friendly for external tools.
> ---------------------------------------------------------------
>
>                 Key: HADOOP-5834
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5834
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Owen O'Malley
>
> Currently, parsing the job history logs with external tools is very difficult because
of the format. The most critical problem is that newlines aren't escaped in the strings. That
makes using tools like grep, sed, and awk very tricky.

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