[
https://issues.apache.org/jira/browse/MAPREDUCE-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13105363#comment-13105363
]
Robert Joseph Evans commented on MAPREDUCE-3002:
------------------------------------------------
It should also be fairly simple to still keep the parts that make since linked
together. We can put all of the common methods into a common interface that
both implement. Then much of the UI can still be shared.
Also I think much of the UI needs to be re-factored. Things like data tables
are everywhere, but the code for them is completely separate. I would like to
see much more work into creating proper widgets that can be used in multiple
places. This would also reduce the need for keeping both UIs tightly linked
because they can both use the same widget, and much of the real code is shared.
> 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
