[
https://issues.apache.org/jira/browse/MAPREDUCE-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12743175#action_12743175
]
Jothi Padmanabhan commented on MAPREDUCE-157:
---------------------------------------------
bq. Is the implicit schema proposed here Map<String,String>?
No, I think it would just be more efficient to preserve the field types.
bq. think side file would be better as it won't bloat each file with the same
info
+1. Since we would have one history file per job and we might need to store the
schema for several events, I think it just makes sense to have a separate file
instead of having them duplicated in each file. The downside is we might have
to store a version number as a header in each history file and read that out of
band before deciding on which version of schema to choose.
> 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.
