hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward Capriolo (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-3307) Hive Web Interfaces Wishes
Date Fri, 27 Jul 2012 13:56:41 GMT

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

Edward Capriolo commented on HIVE-3307:
---------------------------------------

The explain is not two parts it is a normal query processed by the query parser. The reason
it is 'faster' if the query is wrong is because the parsing happens first, if there is a parse
error less work is done, if it passes the parsing phase it has more work to do, some of that
work involves communicating with the metastore so that will take longer. Generally I see explain
take a couple of seconds.If there was a window with an hourglass type thing that let me the
user know to wait for result I thing an async call is fine. 

You could probably just get at the parser and try to parse the query quickly but as far as
I know there is no direct way to do that now.
                
> Hive Web Interfaces Wishes
> --------------------------
>
>                 Key: HIVE-3307
>                 URL: https://issues.apache.org/jira/browse/HIVE-3307
>             Project: Hive
>          Issue Type: Wish
>          Components: Web UI
>            Reporter: Bertrand Dechoux
>            Priority: Minor
>
> List of wishes :
> (I may contribute a few of them.)
> * narrower menu : use span2 instead of span4
> * remove home from menu
> * transform the header "Hive Web Interface" into a link to the home
> * change the "Link" in the header into a hive logo
> * add icons next to Authorize (?/check) to know whether the information was supplied
> * add approximated number of session next to the "list sessions" menu
> * fix history bug
> * add a refresh session in order to have a relatively updated interface
> * add a way to know if the result bucket is outdated (ie for which run, those results
are related)
> * change the with of the query input, it should be width:100%
> * remove select/drop down for running query and use a button instead
> * remove select/drop down for silent mode and add a checkbox
> * find a way to report query error (hack would be with explain command, is there something
only checking the syntax)
> * table description : decorate all key/value entries and do not display empty list

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message