[
https://issues.apache.org/jira/browse/PHOENIX-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14481870#comment-14481870
]
Julian Hyde commented on PHOENIX-971:
-------------------------------------
bq. maybe the naming of the driver and it's module should include the word
"thin", it might make things a bit more clear in the future
I suggest classes PhoenixDriver, PhoenixThickDriver, PhoenixThinDriver,
answering to the "jdbc:phoenix:", "jdbc:phoenix:thick:", "jdbc:phoenix:thin:"
URL prefixes, and also a "flavor" connect string parameter. PhoenixThickDriver,
PhoenixThinDriver are sub-classes containing very little code. PhoenixDriver
has a default value for "flavor", which we may decide to change from one
release to the next.
PhoenixDriver delegates, based on the chosen value of "flavor", to a particular
connection implementation. The connection then serves as the factory for
everything else, e.g. statements, metadata.
> 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
>
> Attachments: PHOENIX-971.00.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)
