hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward Capriolo (JIRA)" <>
Subject [jira] Commented: (HIVE-1668) Move HWI out to Github
Date Fri, 24 Sep 2010 18:46:33 GMT


Edward Capriolo commented on HIVE-1668:

I disagree. The build and test errors are not insurmountable. In fact some if not most of
the "ERRORS" were cascading changes that were not tested properly. For example: was a fix I had to do because someone broke
it here. because someone wanted all jars to
be named whatever.${version} and did not bother to look across all the shell script files
that startup hive. again someone changed some shell scripts and
only tested the cli. again someone broke hwi without testing it., not really anyone's fault but no API stability
across hive. I do not see why one method went away and another similar method took its place.

I have been of course talking about moving HWI to wikit for a while moving from JSP to Servlet/
Java code will fix errors, but the little time I do have I usually have to spend detecting
and cleaning up other breakages.

HUE and Beeswax I honestly do not know, but sounds like you need extra magical stuff to make
this work, and HWI works with hive on its own (onless people break it)

> Move HWI out to Github
> ----------------------
>                 Key: HIVE-1668
>                 URL:
>             Project: Hadoop Hive
>          Issue Type: Improvement
>          Components: Web UI
>            Reporter: Jeff Hammerbacher
> I have seen HWI cause a number of build and test errors, and it's now going to cost us
some extra work for integration with security. We've worked on hundreds of clusters at Cloudera
and I've never seen anyone use HWI. With the Beeswax UI available in Hue, it's unlikely that
anyone would prefer to stick with HWI. I think it's time to move it out to Github.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message