[ https://issues.apache.org/jira/browse/HADOOP-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087783#comment-13087783 ]
Milind Bhandarkar commented on HADOOP-7532: ------------------------------------------- I agree with @atm and others. Hamlet does have some unique capabilities, but it seems to me that it need not be hadoop-specific, and will certainly become a maintenance headache later. So, like Eli, I would like to ask if making it a separate project, and building a community around it, is something you have considered ? Or other choice is to contribute the per-project style rules, and static validation features to an existing popular open source templating engine. But I think the approach described by Robert Evans makes the most sense. Hadoop daemons should expose web-services that exports json/xml, and GUI should be a client. Hadoop management tools at Yahoo and elsewhere have to scrape HTML, which is the problem that needs to be solved. Policies of tags/style enforcement, html validation etc will not remain Hadoop's concern then. > 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