hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jothi Padmanabhan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-1052) In 0.20, JobHistory parsed files using callbacks [Listener]. In 0.21, JobHistoryParser creates a monolithic JobInfo object.
Date Tue, 06 Oct 2009 07:42:31 GMT

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

Jothi Padmanabhan commented on MAPREDUCE-1052:
----------------------------------------------

You could possibly use the EventReader interface to extract the events from the history file
and filter out as required. 

> In 0.20, JobHistory parsed files using callbacks [Listener].  In 0.21, JobHistoryParser
creates a monolithic JobInfo object.
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-1052
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1052
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 0.21.0
>            Reporter: Dick King
>             Fix For: 0.21.0
>
>
> In my opinion, this was a change for the worse.
> I would prefer to bring back the callback interface, at least in addition to the JobInfo
interface, to give API users the option of not creating the whole object if they only want
to glean part of the information.

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