[
https://issues.apache.org/jira/browse/PHOENIX-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14368103#comment-14368103
]
Nick Dimiduk commented on PHOENIX-971:
--------------------------------------
Bumping this thread.
Since my last comment, I've switched workloads, in order to fully emphasize the
impact of the query server overhead. Thus I've not investigated the thread pool
impacts, or suggested resolutions mentioned earlier.
My experiments with HS2 proved fruitless. In the end, the overhead of HS2 was
substantial. I've switched this effort over to Calcite's Avatica, as was
mentioned in an earlier comment. It's a very young implementation, but results
are promising and [~julianhyde] is helping me to fill in the gaps. I'm
optimistic that we'll have what we need supported in a calcite-1.2 release.
Stay tuned.
> 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)
