[
https://issues.apache.org/jira/browse/HIVE-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739363#comment-13739363
]
Thejas M Nair commented on HIVE-4569:
-------------------------------------
[~jaideepdhok] [~cwsteinbach] 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 ? I think [~henryr] has a good point
that it was always documented to be asynchronous (it just happened that it
always was so late in returning the call that the operation was finished :) ).
Also, I think it makes sense to make the GetResultSetMetadata and FetchResults
api blocking until operation finishes, instead of throwing an error if status
is not FINISHED. This will also help to prevent breakage of any user code that
was written with the assumption that execute is blocking.
> 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
