hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hong Tang (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-1016) Make the format of the Job History be JSON instead of Avro binary
Date Wed, 07 Oct 2009 10:50:31 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762994#action_12762994
] 

Hong Tang commented on MAPREDUCE-1016:
--------------------------------------

I think we are misusing version string here. I suggest the version string be "{serializer}-{encoder}-{version}".
E.g. "avro-json-1.0". EventReader should compare only the {serializer} and {version} part
of the string to determine whether a job history file matches (or is compatible with) the
schema of the HistoryInfo object it is about to create - and it would use the {encoder} string
to decide what decoder should be used.

> Make the format of the Job History be JSON instead of Avro binary
> -----------------------------------------------------------------
>
>                 Key: MAPREDUCE-1016
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1016
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Owen O'Malley
>            Assignee: Doug Cutting
>             Fix For: 0.21.0, 0.22.0
>
>         Attachments: MAPREDUCE-1016.patch
>
>
> I forgot that one of the features that would be nice is to off load the job history display
from the JobTracker. That will be a lot easier, if the job history is stored in JSON. Therefore,
I think we should change the storage now to prevent incompatibilities later.

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