hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3002) Delink History Context from AppContext
Date Thu, 15 Sep 2011 06:40:09 GMT

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

Vinod Kumar Vavilapalli commented on MAPREDUCE-3002:

bq. This was used in MR JobHistory to be able to share the UI - all known jobs end up belonging
to a single dummy App.
okay, that is the point I missed completely.

bq. getJob ofc can continue to use the Job interface.
I was concerned that you were going to throw the Job interface away.

Alright, +1 for delinking the HistoryContext from AppContext. Thanks for the clear explanation,

> Delink History Context from AppContext
> --------------------------------------
>                 Key: MAPREDUCE-3002
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3002
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: jobhistoryserver, mrv2
>    Affects Versions: 0.24.0
>            Reporter: Robert Joseph Evans
> Currently the JobHistory Server has a HistoryContext that pretends to be a Map Reduce
ApplicationMaster's AppContext so that UI pages can be shared between the two.  This is not
ideal because the UIs have already diverged a lot, and we have to translate the native History
Server's data into implementations of Job to provide the same interface.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message