hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thejas M Nair (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-4569) GetQueryPlan api in Hive Server2
Date Thu, 15 Aug 2013 17:50:04 GMT

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

Thejas M Nair commented on HIVE-4569:
-------------------------------------

bq. Good luck with that. As soon as you have a couple third-party applications that depend
on this serialization format you will be locked in regardless of how many warnings you place
in the code.
Yes, I agree that risk is very real. Do we want to put these commitments on the still young
hive ? Trying to keep this api backward compatible can be a big burden for hive. Should we
go for something more minimalistic instead ? Just a compile() function instead of getQueryPlan()
like what was put forward in HIVE-4321 ?

bq. 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.
I am ok with having different functions for this. But I think function overloading is a more
natural way of doing this. Deciding whether it should be async or not based on a parameter
seems more natural way of programming, compared to using different functions for that. We
can either have one function with default value or have two with same name. ie, Instead of
ExecuteStatementAsync, I think having a ExecuteStatement with additional isAsync parameter
is more clean. 

                
> 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

Mime
View raw message