[
https://issues.apache.org/jira/browse/PHOENIX-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326743#comment-14326743
]
James Taylor commented on PHOENIX-971:
--------------------------------------
ConnectionQueryServices is not necessarily a singleton. You can create multiple
ConnectionQueryServices, each with their own underlying HConnection by tacking
on a third argument to the connection URL like this:
{code}
jdbc:phoenix:localhost:a
jdbc:phoenix:localhost:b
{code}
Multiple thread pools is almost always a bad idea. We want to bound the work
across all queries. The size of the thread pool and its depth is configurable:
{code}
phoenix.query.threadPoolSize
phoenix.query.queueSize
{code}
> Query server
> ------------
>
> Key: PHOENIX-971
> URL: https://issues.apache.org/jira/browse/PHOENIX-971
> Project: Phoenix
> Issue Type: New Feature
> Reporter: Andrew Purtell
> Assignee: Nick Dimiduk
> Fix For: 5.0.0
>
>
> Host the JDBC driver in a query server process that can be deployed as a
> middle tier between lighter weight clients and Phoenix+HBase. This would
> serve a similar optional role in Phoenix deployments as the
> [HiveServer2|https://cwiki.apache.org/confluence/display/Hive/Setting+Up+HiveServer2]
> does in Hive deploys.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
