[
https://issues.apache.org/jira/browse/HIVE-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12696182#action_12696182
]
Namit Jain commented on HIVE-385:
---------------------------------
If you separating the compile and execute, why not go towards ODBC/OCI kind of
approach ?
Have a equivalent of a StatementHandle, set the command in that -
compile/execute takes the StatementHandle as an input.
The QueryPlan can automatically be retrieved from the StatementHandle.
This way, automatically you can handle interleaved queries - I mean, compile
query1, compile query2, execute query 1 etc.
You should initialize all the state (session variables) at the beginning of
compile/execute from the statement handle.
> Split Driver.run() into compile() + exec()
> ------------------------------------------
>
> Key: HIVE-385
> URL: https://issues.apache.org/jira/browse/HIVE-385
> Project: Hadoop Hive
> Issue Type: Improvement
> Components: Query Processor
> Reporter: Neil Conway
> Assignee: Neil Conway
> Attachments: hive_driver_compile.patch
>
>
> Currently, Driver.run() parses, analyzes, and then executes a given query
> string. This isn't very flexible: it would be nice to be able to parse and
> analyze a query to get a query plan, and then execute that query plan at a
> later time (zero or more times). This would also be a necessary prerequisite
> for supporting server-side prepared statements.
> I'd like to change Driver as follows:
> * Add a new method Driver.compile(String), which parses and analyzes the
> given query string, and returns an object representing the planned query
> * Add a new method Driver.execute(Plan), which runs the given planned query
> * Reimplement run(String) as { p = compile(String); execute(p); }
> Comments welcome; I should have a candidate patch ready soon.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
