[
https://issues.apache.org/jira/browse/HIVE-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13642418#comment-13642418
]
Thejas M Nair commented on HIVE-4321:
-------------------------------------
bq. ODBC uses the term "Prepare" instead of "Compile", and I think we should
do the same thing here.
It would make sense to use 'prepare' if we are trying to address the 'prepare'
+ 'executePrepared' use case. Unlike OLTP oriented databases, where
prepare+executePrepared are going to be useful for doing things like large
number of single row inserts, it is not going to be as useful in hive.
My main worry is that this use case would add more state to be stored in hive
server. Once we add support for high-availability, maintaining additional state
on hive server 2 would come at additional costs (I am worried about costs of
storing the whole plan in something like an rdbms or zookeeper).
Also, calling it 'prepare' without supporting 'prepare' + 'executePrepared' use
case is going to be misleading. I think the feature supported by this api is
better conveyed by 'compile'.
HS2 is now a single point of failure in the system, I think we should start
considering high-availability issues while adding features. Keeping state in
client instead of server will help with that.
> Add Compile/Execute support to Hive Server
> ------------------------------------------
>
> Key: HIVE-4321
> URL: https://issues.apache.org/jira/browse/HIVE-4321
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2, Thrift API
> Reporter: Sarah Parra
> Assignee: Sarah Parra
> Attachments: CompileExecute.patch
>
>
> Adds support for query compilation in Hive Server 2 and adds Thrift support
> for compile/execute APIs.
> This enables scenarios that need to compile a query before it is executed,
> e.g. and ODBC driver that implements SQLPrepare/SQLExecute. This is commonly
> used for a client that needs metadata for the query before it is executed.
--
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
