phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-971) Query server
Date Thu, 12 Feb 2015 21:45:12 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14319041#comment-14319041
] 

Andrew Purtell commented on PHOENIX-971:
----------------------------------------

I'm not sure HS2 is the best choice. Apache Calcite offers similar components (although maybe
less featureful) but bills itself as common/neutral infrastructure, and is used in many places.
It's not code beholden to the priorities of one project, not in the way HS2 is. I'd expect
HS2 first and foremost (maybe exclusively?) to evolve to fit the needs of the Hive project.
I'm not sure Hive cares about Phoenix much one way or the other. If they don't care, that's
a potential problem. If some in that camp do care and see Phoenix as competition, that's also
a potential problem. HS2 might work today but at the next major release of Hive who can say.


> 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
>
>
> 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)

Mime
View raw message