incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Purtell <>
Subject Re: [PROPOSAL] Phoenix for Incubation
Date Thu, 14 Nov 2013 17:41:36 GMT
On Wed, Nov 13, 2013 at 10:50 PM, Henry Saputra <>wrote:

> It is indeed very specific for HBase use I suppose. Would it be more
> beneficial to make it sub-project of HBase to get full community
> support from HBase?

I'm on the HBase PMC and am enthusiastically +1 for incubation of Phoenix
to become a TLP.

Phoenix can be divided into a front end and a back end.

The front end is delivered as a JDBC driver and contains, among other
things, the SQL parser and query planner. The front end is currently
written for the HBase client API but could be extended to support other
data stores in the Apache family.

The back end is, currently, HBase specific components for pushing as much
work to the server as possible. However, if there were sufficient interest
to build them, contributions to Phoenix of new back ends for other data
stores in the Apache family would be feasible.

Most importantly, as James mentioned in the proposal, much of the Phoenix
project's attention will focus on the query planning part. Supporting SQL
or any declarative query interface is to the best of my knowledge a
non-goal of the HBase community.

Best regards,

   - Andy

Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message