[
https://issues.apache.org/jira/browse/HIVE-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12914669#action_12914669
]
Edward Capriolo commented on HIVE-1668:
---------------------------------------
{quote}That's not a great argument for keeping code that's onerous to maintain
in trunk.{quote}
Its not onerous to maintain. As you can see from the tickets I pointed out it
broke because it was not tested.
For example,
https://issues.apache.org/jira/browse/HIVE-752 when designing SHIM classes that
specify a classname in a string, one has to make sure they get the class name
correct. I know it was an over site, but I am sure someone fired up the CLI and
made sure the class name was correct.
As for https://issues.apache.org/jira/browse/HIVE-978, I specifically mentioned
how to test this any why it should be tested in the patch and it still turned
out not to work right.
pragmatic is the perfect word. HWI was never made to be fancy. Anyone who has
hive can build and run the web interface. With no extra dependencies. It looks
like to use Beeswax you need Hue, which means you need to go somewhere else and
get it and install it. It seems like you need to patch or load extra plugins to
your namenode and datanode like org.apache.hadoop.thriftfs.NamenodePlugin, It
looks like (http://archive.cloudera.com/cdh/3/hue/manual.html#_install_hue) you
need:
gcc gcc
libxml2-devel libxml2-dev
libxslt-devel libxslt-dev
mysql-devel librarysqlclient-dev
python-devel python-dev
python-setuptools python-setuptools
sqlite-devel libsqlite3-dev
The pragmatic approach, is to use the web interface provided by hive. You do
not need anything external like python, or have to make any changes to their
environment. That is why I think we should stay part of the hive distribution.
I'm -1 on taking it out.
> 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.
