[
https://issues.apache.org/jira/browse/PHOENIX-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14486749#comment-14486749
]
James Taylor commented on PHOENIX-971:
--------------------------------------
I'm not wed at all to the {{jdbc:phoenix://}} - I just wasn't sure this was a
standard or not. I like [~julianhyde]'s suggestion, though, and I don't think
it'd be too much work. When we parse the third part of the connection string
url (see PhoenixEmbeddedDriver.ConnectionInfo.create(String url)), we can check
if it's a value of one of the "flavor" enums. If not, we can use the "default"
flavor (which would be thick for now). Just refactor the ConnectionInfo class
as it's own top level class.
I do think it's important that we have the kind of url we want in the beginning
as folks rely on this kind of thing (and it's painful to change later)..
> 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)
