[
https://issues.apache.org/jira/browse/HIVE-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13642186#comment-13642186
]
Carl Steinbach commented on HIVE-4321:
--------------------------------------
The Thrift API, as well as the CLIService API, is closely modeled on the ODBC
API (and by extension JDBC). ODBC uses the term "Prepare" instead of "Compile",
and I think we should do the same thing here. In other words, the new Thrift
method should be called PrepareStatement() instead of Compile().
I think we also need to consider how this will impact OperationState and
TOperationState. For example, do we need to add additional states? ODBC and
JDBC allow a prepared statement to be executed multiple times, and they also
support the ability to bind input parameters after the statement has been
compiled. We don't have to support that right now, but any API changes we make
should take this use case into account.
I plan to look at this more closely over the weekend and will probably have
some more feedback at that point.
> 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
