[
https://issues.apache.org/jira/browse/HIVE-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13742735#comment-13742735
]
Vaibhav Gumashta commented on HIVE-4569:
----------------------------------------
[~ashutoshc][~henryr][~jaid...@research.iiit.ac.in] [~thejas] I definitely
think execute async is quite ready and would be a good idea to have that in,
while we discuss concerns on GetQueryPlan/TaskStatus. Without splitting, it
might be kind of hard to focus on each. While reviewing this patch, I was
actually trying to group the changes in two sets - I have a document which kind
of summarizes the changes of each group (1. ExecuteAsync 2. GetQueryPlan +
TaskStatus). I can upload that if you guys find use for it (if we decide on
splitting, we can use it to see what we want in each JIRA).
> 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,
> HIVE-4569.D12333.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
