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

Edward Capriolo commented on HIVE-30:
-------------------------------------

There is one more thing it should handle if it does not do already. If a user 
issues a large query where does the intermediate data go? And how much of it 
should be kept? For example a user from the web interface may issues a query 
like "SELECT people.* FROM people. Lets assume this results in 2GB of results. 
If I were using a command line interface I would expect the data to be stream 
to my console. If I were using a web interface I would expect that data to be 
saved somewhere. Currently, HWI is saving the the data to a local file. I was 
thinking to implement a FIFO queue that would hold a variable number of rows in 
memory.  Or a similar setting that would clean up the file. A JDBC style driver 
with a cursor is still and issue because it will be blocked until the user 
returns for that data, which could be never. Most queries will end up creating 
a new table of file in HDFS so its not a major issue. 

Above someone mentioned not being able to take advantage of Fair Share 
scheduling and tables names. I think you can do that from the HWI interface. 
The user has access to the SetProcessor through a JSP page, so they should be 
able to set and hive/hadoop variables from HWI. There is nothing stopping me 
from using someone else's credentials, however the same is true for the hive 
CLI. Correct?

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

Reply via email to