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-5834) Job History log file format is not friendly for external tools.
Date Fri, 15 May 2009 08:10:45 GMT

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

Amar Kamat commented on HADOOP-5834:
------------------------------------

I think for now we can do something like this 
{code}
# encoding step
1. escape all ';' in values
2. replace '\n' with ';'

# decoding step
1. replace all unescaped ';' with \n
2. unescape all ';'
{code}

For now this should work. Externally the error message would look like ';' separated values
and one line in jobhistory will contain exactly one event. Thoughts?

> 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