hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward Capriolo (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4514) Hive web interface
Date Fri, 07 Nov 2008 15:25:05 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-4514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645790#action_12645790

Edward Capriolo commented on HADOOP-4514:

The hwi-site and hwi-default set three variables
hwi.war.file = /opt/hive/lib/hwi.war path to the war for the web application. This is passed
to jetty as it is started up.
hwi.listen.host= listen on all interfaces
hwi.listen.port=9999 the port the jetty server will start on.

Theoretically there could be more in the future.

If you do not want separate configuration files hwi could pull them from the hive-site. I
have avoided patching any upstream files. If you want to add those properties upstream I am
cool with that.

I am not sure of the time line on the JDBC drivers. I do not want to to be a blocker issue.
When the JDBC drivers are mature I suggest this simple technique of  having both of them work
from the web interface.

Right now a SessionItem manages the CLISessionState.
We create a JDBCSessionItem that manages a JDBC session.

Both of them can have a parent class AbstractSession, any shared properties like QUERY can
be defined in the parent class. The webserver manages long running queries,  the results may
need to be written to a file. The function is the same, submit and manage, just the internals
are handled with a resultSet rather then an output stream.

Thank you for the tip on the JobName.


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

View raw message