hadoop-hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Hammerbacher (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HIVE-1668) Move HWI out to Github
Date Fri, 24 Sep 2010 21:22:36 GMT

    [ https://issues.apache.org/jira/browse/HIVE-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12914653#action_12914653
] 

Jeff Hammerbacher commented on HIVE-1668:
-----------------------------------------

bq. Are you guys contributing Hue to ASF?

No.

bq. It seems hasty to remove functionality in favor of a replacement if that replacement isn't
going to be shipped with mainline Hive. 

There's certainly precedent in other projects. For example, indexed HBase was moved out to
Github for very similar reasons: while it provided a useful feature, it did so in a somewhat
flaky way.

bq. I have learned to roll with the punches.

That's not a great argument for keeping code that's onerous to maintain in trunk.

Just trying to be pragmatic here.

> 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.


Mime
View raw message