[ https://issues.apache.org/jira/browse/HIVE-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13738575#comment-13738575 ]
Vaibhav Gumashta commented on HIVE-4569: ---------------------------------------- It seems that this JIRA is handling two different use cases: 1. Implement ExecuteStatement asynchronously (and the related GetOperationStatus api) 2. Implement GetQueryPlan api. I see that these are fairly independent features. How about we split it into 2 JIRAS to have independent focussed discussion? Also, I can volunteer to continue the work. Thanks. > 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 > > > 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