hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jaideep Dhok (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-4569) GetQueryPlan api in Hive Server2
Date Thu, 04 Jul 2013 05:06:21 GMT

    [ https://issues.apache.org/jira/browse/HIVE-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13699773#comment-13699773
] 

Jaideep Dhok commented on HIVE-4569:
------------------------------------

{quote}
Thrift makes it easy to add additional optional parameters without breaking backward compatibility,
but not Java. I'd recommend creating a new executeStatementAsync call to ICLIService (and
here) instead of modifying the method signature. Also, that probably indicates that we should
add a new complimentary RPC to the HS2 Thrift IDL instead of using adding an optional parameter
to ExecuteStatement just to keep these things in sync.
{quote}

Do we need explicit new request and response objects for both executeStatement and executeStatementAsync
calls? I think the same request call should do?

Also, I found in the code that conf overlay is not actually being applied before executing
an operation. I suppose there should be another JIRA for that.


                
> 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

Mime
View raw message