Mailing-List: contact hive-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hive-dev@hadoop.apache.org
Message-ID: <899019843.1227306104342.JavaMail.jira@brutus>
Date: Fri, 21 Nov 2008 14:21:44 -0800 (PST)
From: "Joydeep Sen Sarma (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Subject: [jira] Commented: (HIVE-30) Hive web interface
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

ok - i filed hive-77. i think it makes sense to do any multi-threading cleanup in a separate jira (since that could be an issue for other server code as well). also we need a good test suite for this kind of execution environment.

if u can make progress on some of the other issue - i can take a stab at hive-77 in parallel. 

regarding the username vs. session: would it be fair to say that passwords are usually on a per user basis. ie. i am wondering if the flow should be 'specify username/password' and then 'start new session', 'list sessions' etc. - all within the context of one userid. i am a little skeptical of the 'set' approach - i think most people will not set anything unless they have to. for the administrator - it's critical that userid be set - otherwise all load on the map-reduce cluster and all tables look like they are owned by one user - which is pretty terrible.

I understand that this can be easily faked - but at least it sets expectations and sets up for future ldap etc. integration. Perhaps others can chime in here as well?


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