[
https://issues.apache.org/jira/browse/HADOOP-4514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643055#action_12643055
]
Edward Capriolo commented on HADOOP-4514:
-----------------------------------------
Inside Hadoop components like NameNode implement HttpServlet directly.
I think we should replicate the bin/hive to bin/hiveweb this would kick off a
management application.
$hadoop/webapps/hiveweb would be the home for the JSP files
I think we should have a Threaded application running inside the servlet
engine.
If a user runs a query that would have output to the console we should save
that data into temporary file?
If so where would that data be save?
How long before if should be cleaned up?
If it creates a temporary file should we impose a limit on the size? Select *
could be really big where would that
local data go?
We could offer a browse of the database by using the meta information and the
HDFS files directly? A simple Next 100 Previous 100.
> Hive web interface
> ------------------
>
> Key: HADOOP-4514
> URL: https://issues.apache.org/jira/browse/HADOOP-4514
> Project: Hadoop Core
> Issue Type: New Feature
> Components: contrib/hive
> Reporter: Jeff Hammerbacher
> Priority: Minor
>
> Hive needs a web interface. The initial checkin should have:
> * simple schema browsing
> * query submission
> * query history (similar to MySQL's SHOW PROCESSLIST)
> A suggested feature: the ability to have a query notify the user when it's
> completed.
> Edward Capriolo has expressed some interest in driving this process.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
