[
https://issues.apache.org/jira/browse/HADOOP-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087315#comment-13087315
]
Eli Collins commented on HADOOP-7532:
-------------------------------------
Re-implementing templating engine feels out of scope to me as well. My main
concern is not about the quality of Hamlet - I assume it's good stuff - but
that a Hadoop-only web framework is not going to be actively advanced like
other projects and so in a couple of years we'll be on something that's pretty
out of date and that only a small number of people know how to change (like our
RPC library and serialization framework).
Luke - have you considered making Hamlet into a separate project and having
Hadoop consume this project? I'd be less worried about the above if there was a
community built around Hamlet. The advantages of Hamlet you've outlined should
make it useful to any project and therefore would attract a community.
Similarly, if MR is the only project willing to adopt Hamlet then I wonder if
it's a wise choice.
> Hadoop web UI 2.0
> -----------------
>
> Key: HADOOP-7532
> URL: https://issues.apache.org/jira/browse/HADOOP-7532
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 0.23.0
> Reporter: Luke Lu
> Assignee: Luke Lu
> Fix For: 0.23.0
>
>
> People have expressed interests of bringing Hadoop web UI up to date with the
> lightweight embedded web mvc framework used in MAPREDUCE-279 (cf.
> MAPREDUCE-2399). This is the umbrella jira for UI improvement for 0.23+.
> Individual items like web framework refactor/move and the unique challenge
> for MR2 webapp security will be filed separately.
> Thoughts/ideas on various improvement of Hadoop web UI are welcome here. Some
> of the ideas will naturally become sub-issues.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
