[
https://issues.apache.org/jira/browse/PHOENIX-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14237055#comment-14237055
]
Lars Hofhansl commented on PHOENIX-971:
---------------------------------------
Let's also discuss if/how we can avoid having to deploy, orchestrate, monitor,
etc, another Phoenix service for HBase. It's already a pain in the a** to run
all the required services.
The key here to avoid client side jar management. It seems if we "just" had a
way for a client to detect cluster topology we could handle everything else
with coprocessor endpoints. See HBASE-12126...
Maybe. Have to make we do not need all of the HBase client plumbing.
> Query server
> ------------
>
> Key: PHOENIX-971
> URL: https://issues.apache.org/jira/browse/PHOENIX-971
> Project: Phoenix
> Issue Type: New Feature
> Reporter: Andrew Purtell
>
> 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)
