[
https://issues.apache.org/jira/browse/HIVE-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13741324#comment-13741324
]
Thejas M Nair commented on HIVE-4569:
-------------------------------------
bq. Whether or not this makes more sense than the current approach hinges
largely on how many more optional variables we expect to add to the
ExecuteStatement[Async] request messages in the future.
I think it is reasonable to expect the unexpected, ie expect more optional
parameters coming up in future.
This is what I am thinking. [~cwsteinbach] Please let me know if you think this
is reasonable.
1. In TCLDriver.thrift, as in the original patch, add "optional bool runAsync"
to TExecuteStatementReq
2. In ICLIService (and its implementation CLIService), introduce a executeAsync
function that gets called if runAsync==true.
> 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
