[
https://issues.apache.org/jira/browse/PHOENIX-971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated PHOENIX-971:
---------------------------------
Attachment: PHOENIX-971.01.patch
[~julianhyde] that approach sounds like it'll take some refactoring in Phoenix.
Let's hold off on that until we have Calcite further integrated throughout
Phoenix.
[~jamestaylor] regarding the jdbc url string, I'll do whatever you guys think
is best. The {{://}} bit is a little strange because Avatica connection strings
include a {{url}} component that itself specifies a protocol. If you really
like the idea of {{jdbc:phoenix://}}, maybe we can include a {{;protocol=}}
component that we can parse to use when building the Avatica connection string.
I think that may be too complicated, but I don't know what JDBC drivers usually
do here.
Here's a patch that adds a test explicitly checking cohabitation of these
drivers. I also better support passing Avatica configuration parameters down to
the underlying JdbcMeta implementation.
Maybe [~mujtabachohan] can help me work out why my use of the
build-helper-maven-plugin is including {{src/it}} on the class path during
regular test phase.
> 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: PHOENIX-971.00.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)
