[
https://issues.apache.org/jira/browse/HIVE-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649771#action_12649771
]
Edward Capriolo commented on HIVE-30:
-------------------------------------
>>hwi shell script:
I see what you are saying. Ill add this capability. This would make the hive
script work more like /bin/hadoop
>>I think it will be fairly critical to take in userids and propagate them to
>>hive/hadoop (by setting user.name property).
Once you have started the hive session. You have access to the set processor.
You should be able to do. SET user.name=ecapriolo. I could make a form to this
effect to make setting these things easier, but the session_set_processor.jsp
allows for set commands.
>>Another thing i just noticed - Hive's current runtime assumes a singleton
>>SessionState object.
I had not looked deep into that part of the API. That would block me. I guess
it did not come up on any ones radar till now.
>>why don't we just replace 'sessionname' with 'userid' ?
I was looking at this like a user can have more then one session, that being
the case a name would identify it.
>>please set the session to silent mode.
Sounds good. I figured most queries would output to a HDFS file. I viewed the
result file as a good way to debug. A normal user would expect whatever came
out of the CLI to be in the results file. I will add a debug switch. In the API
>>how was this tested?
Me and a live server. Smaller data sets, simple queries. I did not pick up on
the 'singleton SessionState object' issue.
>>any reason why QUERY_SET etc. should not be an enum type?
I'm just old school. I will change it to enum.
> 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.
