[
https://issues.apache.org/jira/browse/PHOENIX-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14487694#comment-14487694
]
Julian Hyde commented on PHOENIX-971:
-------------------------------------
Just remember that if there are multiple JDBC drivers they might be registered
in any order. So the less specific ones (e.g. jdbc:phoenix:) have to be careful
not to accept connections that can be handled by more specific ones (e.g.
jdbc:phoenix:thin:).
> 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: 4.4.0
>
> Attachments: 971-secure-login-1.patch, 971-secure-login.patch,
> PHOENIX-971.00.patch, PHOENIX-971.01.patch, PHOENIX-971.01.patch,
> PHOENIX-971.01.patch, image-2.png
>
>
> 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)
