[
https://issues.apache.org/jira/browse/MAPREDUCE-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745279#action_12745279
]
eric baldeschwieler commented on MAPREDUCE-157:
-----------------------------------------------
Re: AVRO conversion
Doug and I chatted. My concern is that we are working through a job history
refactor with a bunch of moving parts. I want to get those all into 21 and
stable. Until that is done I don't want to consider AVRO since it might put
that rework at risk (since our team has already invested in JSON). That said,
I'm not against binary AVRO here. It could have advantages. If someone else
can put in the time to demonstrate that this will work, I think that might be a
better approach. I just hope we can do that as a distinct patch that follows
this one.
(Or collaborate to make one patch, we just don't have the resources before 21
freeze)
(For the wider context of the refactor, see MAPREDUCE-863)
> 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
> Reporter: Owen O'Malley
> Assignee: Jothi Padmanabhan
>
> 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.
