You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Owen O'Malley (JIRA)" <ji...@apache.org> on 2009/05/15 05:00:45 UTC

[jira] Commented: (HADOOP-5834) Job History log file format is not friendly for external tools.

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

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

The current format quotes the character set ["\.]. The format is 

key kind1="val1" kind2="val2"\n

with newlines in the values converted to '\n' and quotes converted to '\"'. We should also consider how to represent counters better. The current format is pretty painful.

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