hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jaideep Dhok (JIRA)" <>
Subject [jira] [Commented] (HIVE-4569) GetQueryPlan api in Hive Server2
Date Wed, 14 Aug 2013 08:07:54 GMT


Jaideep Dhok commented on HIVE-4569:

bq. Having a new phabricator link for each patch iteration makes it difficult to follow the
changes between patches.
Looks like the changes got split into two requests.
Unfortunately I am unable to update the previous revision, as I had lost the previous arc
commit. I will put up a new  request, and keep updating it if there are further comments?

bq.  Should we keep the api simple (small) by just making the current execute function asynchronous
instead of adding an additional execute function in the api ?

[~thejas] I think making executeStatement async by default may break users' expectations since
it's a blocking call. [~cwsteinbach] Had suggested earlier to create two separate calls executeStatement
and executeStatementAsync so that the API is easier to understand. I agree with that approach.
If we have two different calls, then users can pick one based on their need.

For getting result set in case of async the flow would be - ExecuteStatementAsync, GetOperationStatus
(until query completes), then fetch result set. 
> GetQueryPlan api in Hive Server2
> --------------------------------
>                 Key: HIVE-4569
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2
>            Reporter: Amareshwari Sriramadasu
>            Assignee: Jaideep Dhok
>         Attachments: git-4569.patch, HIVE-4569.D10887.1.patch, HIVE-4569.D11469.1.patch,
HIVE-4569.D12231.1.patch, HIVE-4569.D12237.1.patch
> It would nice to have GetQueryPlan as thrift api. I do not see GetQueryPlan api available
in HiveServer2, though the wiki
contains, not sure why it was not added.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message