Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Thu, 18 Aug 2011 00:57:27 +0000 (UTC)
From: "Aaron T. Myers (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <667525361.47399.1313629047539.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <550363210.21720.1312925669268.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HADOOP-7532) Hadoop web UI 2.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086713#comment-13086713 ] 

Aaron T. Myers commented on HADOOP-7532:
----------------------------------------

Hey Luke, I realize this feedback is really late to the game, but I remain unconvinced that introducing a novel web framework into the Hadoop codebase is necessary.

Most of the reasons you provided previously in MAPREDUCE-2399 seem to be against MVC frameworks as a whole because Hadoop really only needs a templating engine with a little bit of controller help. I agree Hadoop probably shouldn't incorporate a full-blown MVC framework, but there exist several template-only frameworks out there which might work. Can you perhaps enumerate which existing libraries you looked at, and why you ruled them out? In particular, did you look at Jamon? (http://www.jamon.org/)

Furthermore, I don't find the "every Java developer can pickup [Hamlet] without having to learn any new (expression) language syntax" argument terribly compelling. Developers who want to make changes to a Hadoop web page will now need to learn Hamlet, which has its own set of things to learn, and presently has a dearth of documentation, developers with experience using it, or a community supporting it. Using Hamlet for all Hadoop web UIs also serves to hinder many developers who do have some familiarity with HTML and already-existing templating engines. From looking at the code which uses Hamlet in MR-279, it honestly seems to me to be strictly _more_ confusing than using a traditional templating system.

To be completely clear here, I'm not vetoing this. I'm mostly trying to play the devil's advocate. The Hadoop project has re-invented many wheels, and I'm skeptical we need to re-invent the web templating wheel as well.

> 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