[
https://issues.apache.org/jira/browse/HIVE-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649184#action_12649184
]
Ashish Thusoo commented on HIVE-30:
-----------------------------------
I don't completely understand the show processlist thingy that you are
mentioning here. I am not sure if there is a show processlist notion here. Are
you talking about SessionItem? I think that you have a completely stateless
implementation where the execute and fetch is all done within the http call but
then you would still need to maintain state somewhere if you want to share the
session results (hipal does this persistently through mysql while here there is
a transient state maintained in the SessionItem set in the server). Are you
referring to the SessionItem set when you talk about processlist?
Regarding the userid and authentication stuff, I think the best there is to use
pam based scheme to tie this in with an existing LDAP repository or unix
accounts. But that can perhaps be done as a follow up transaction?
> 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.