[
https://issues.apache.org/jira/browse/PHOENIX-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14205583#comment-14205583
]
James Taylor commented on PHOENIX-971:
--------------------------------------
Since each RS can act as a Phoenix client, we could implement a thin client
that sends the query from the client to the RS which would most likely handle
at least part of the query. We could keep enough logic on the client-side to
determine the start/stop row of the scan so that we'd know *where* to send the
query. There's already an optimization in place to run scans/puts locally (i.e.
bypassing the RPC stack when possible), so this would minimize any extra
network hops. The rest of the work now being done on the client (i.e.
parallelization) could be done on the RS.
> 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)
