[
https://issues.apache.org/jira/browse/MAPREDUCE-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13104359#comment-13104359
]
Vinod Kumar Vavilapalli commented on MAPREDUCE-3002:
----------------------------------------------------
Not sure why we want to do this. Sharing the UI pages is not the primary goal
of this use of same interfaces - Context, Job etc. Logically, a Job's behaviour
shouldn't change once it is in history, except for its liveliness. I don't
think the current Job interface has much tied to its liveliness, it actually
shouldn't be unnatural to serve History data via the same interface.
Or may be I am missing something, you have particular issues in your mind?
As a side note, I am strongly in favour of sharing the UI's too given our
experience on how divergent and disconnected they were in MRV1. Note that we
can still have the UI code different but with the user-experience consistent.
Just saying.
> 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
