[
https://issues.apache.org/jira/browse/HIVE-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740811#comment-13740811
]
Carl Steinbach commented on HIVE-4569:
--------------------------------------
bq. Thejas M Nair I think making executeStatement async by default may break
users' expectations since it's a blocking call. Carl Steinbach 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.
It's possible to overload ExecuteStatement to support both synchronous and
asynchronous modes without breaking backward compatibility by adding an
optional boolean isAsync flag to the request message and setting the default
value to false. 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. If we have two
functions then we'll need to make the same changes in two different places.
> 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
