[
https://issues.apache.org/jira/browse/MAPREDUCE-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755625#action_12755625
]
Doug Cutting commented on MAPREDUCE-157:
----------------------------------------
I will move the Avro port of this to MAPREDUCE-980. I do not want to impede
progress here.
> Doug, so your patch will store binary AVRO?
Yes. Avro 1.0 (the current release) only supports binary.
Avro 1.1 (out today if it can get one more PMC +1, please) adds JSON i/o.
Printing the log as JSON will be easy if I can upgrade Hadoop to Avro 1.1 in
MAPREDUCE-980.
> Job History log file format is not friendly for external tools.
> ---------------------------------------------------------------
>
> Key: MAPREDUCE-157
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-157
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Affects Versions: 0.20.1
> Reporter: Owen O'Malley
> Assignee: Jothi Padmanabhan
> Fix For: 0.21.0
>
> Attachments: mapred-157-10Sep.patch, mapred-157-15Sep-v1.patch,
> mapred-157-15Sep.patch, mapred-157-4Sep.patch, mapred-157-7Sep-v1.patch,
> mapred-157-7Sep.patch, mapred-157-prelim.patch, MAPREDUCE-157-avro.patch,
> MAPREDUCE-157-avro.patch
>
>
> 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.
