[
https://issues.apache.org/jira/browse/HIVE-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700954#action_12700954
]
Neil Conway commented on HIVE-80:
---------------------------------
A reasonable way to implement this might be as follows:
* Change the HiveServer#execute() method to return a unique ID for each active
query (this can just be QueryPlan#getQueryId()).
* Change the rest of the HiveServer methods to be parameterized by the query ID
* Inside HiveServer, create a separate Driver object for each active query
* Perhaps add a HiveServer#close() method that clients can use when they're
finished executing a query
One issue is that if a client dies spontaneously, it might not call close(),
which would leak resources at the server.
Comments? If you're not working on this right now Raghu, I'd be happy to take a
crack at it.
> Allow Hive Server to run multiple queries simulteneously
> --------------------------------------------------------
>
> Key: HIVE-80
> URL: https://issues.apache.org/jira/browse/HIVE-80
> Project: Hadoop Hive
> Issue Type: Improvement
> Components: Server Infrastructure
> Reporter: Raghotham Murthy
> Assignee: Raghotham Murthy
> Priority: Critical
> Fix For: 0.4.0
>
>
> Can use one driver object per query.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
