[
https://issues.apache.org/jira/browse/HIVE-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740809#comment-13740809
]
Carl Steinbach commented on HIVE-4569:
--------------------------------------
[~jaideepdhok] If I call GetQueryPlan for a statement x, and then subsequently
call ExecuteStatement on the same statement, is it guaranteed that
ExecuteStatement will always use the same plan that was returned earlier by
GetQueryPlan? The names of the functions seem to imply this, but the comments
in TCLIService.thrift don't stipulate that ExecuteStatement will use the plan
generated by the previous GetQueryPlan call instead of recompiling the
statement and possibly creating a different plan. Adding a PrepareStatement
call (e.g. PrepareStatement[, GetQueryPlan], ExecuteStatement) is one way of
resolving this ambiguity, and at the same time it will help to maintain the
close alignment between the HS2 API and ODBC/JDBC.
> GetQueryPlan api in Hive Server2
> --------------------------------
>
> Key: HIVE-4569
> URL: https://issues.apache.org/jira/browse/HIVE-4569
> 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
> https://cwiki.apache.org/confluence/display/Hive/HiveServer2+Thrift+API
> 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: http://www.atlassian.com/software/jira
