hadoop-hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joydeep Sen Sarma (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HIVE-30) Hive web interface
Date Thu, 20 Nov 2008 08:50:44 GMT

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

Joydeep Sen Sarma commented on HIVE-30:
---------------------------------------

@Edward - the thrift Hive Server is implemented in Java - all that C++ code is generated thrift
code for the client side stubs in all likelihood.

@ashish - from what i see - the thrift hiveserver does not manage sessions right now. I think
at this point we are all in agreement and perhaps we should spec out what the hive session
manager common to all access paths does:

  - start/stop session
  - validate user credentials and maintain stats/logs per user/session
  - compile queries
  - submit any map-reduce jobs

submitting a map-reduce task by itself is low overhead - and also desirable in the session
manager (so that an admin can come to the session manager and see and kill running map-reduce
jobs). however - beyond this - any actual reading of the data files ought to definitely occur
in the client (ie. cli/jdbc server/hwi). 

given that the thrift server does not manage sessions right now - and the current patch has
the beginnings of a session manager - we could as well begin here by teasing apart the generic
session management code/server and then starting to adapt other clients to it .. 

comments?

> Hive web interface
> ------------------
>
>                 Key: HIVE-30
>                 URL: https://issues.apache.org/jira/browse/HIVE-30
>             Project: Hadoop Hive
>          Issue Type: Bug
>            Reporter: Jeff Hammerbacher
>            Assignee: Edward Capriolo
>            Priority: Minor
>         Attachments: HIVE-30.patch
>
>
> 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.


Mime
View raw message