[
https://issues.apache.org/jira/browse/HIVE-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12914605#action_12914605
]
Edward Capriolo commented on HIVE-1668:
---------------------------------------
Plus, not to get too far off topic, but there is a huge portion of the hadoop
community that thinks "Security? So what? Who cares?" I am not going to run
Active Directory or Kerberos just so I can say "My hadoop is is secure" . It
adds latency to many processes, complexity to the overall design of hadoop, and
does not even encrypt data in transit. Many people are going to elect not to
use "hadoop security" for those reasons. Is "extra work" a reason not to do
something? Are we going to move the Hive Thrift server out to github too
because of the burden of "extra work"? It is a lot of extra work for me when
hadoop renames all its jmx counters or tells me "all my code is deprecated
because of our new slick mapreduce.* api". I have learned to roll with the
punches.
> 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.
