[
https://issues.apache.org/jira/browse/HIVE-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12914741#action_12914741
]
Edward Capriolo commented on HIVE-1668:
---------------------------------------
{quote}It should also help mature the product for eventual inclusion in
trunk.{quote}
Why would we move something from hive out to github, just to move it back to
hive?
{quote}Empirically, they don't. The value of the web interface to users is not
nearly as high as the pain it causes the developers for maintenance.{quote}
Who are these developers who maintain it? Has anyone every added a feature
beside me? I'm not complaining.
http://blog.milford.io/2010/06/getting-the-hive-web-interface-hwi-to-work-on-centos/
{quote}The Hive Web Interface is a pretty sweet deal.{quote}
Sounds like people like it.
Why are we debating the past state of hwi? It works now. If someone reports a
bug I typically investigate and patch that same day.
I challenge anyone to open a ticket on core user, called "remove name node web
interface to github" and tried to say "XXXX now offers a better name node
interface using python." The ticket would instantly get a "RESOLVED: WILL NOT
FIX". Why is this any different?
> Move HWI out to Github
> ----------------------
>
> Key: HIVE-1668
> URL: https://issues.apache.org/jira/browse/HIVE-1668
> 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.
