incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nick Dimiduk <>
Subject Re: [VOTE] Phoenix for incubator project
Date Sat, 07 Dec 2013 22:37:23 GMT
+1 from me; Phoenix is good for HBase and Apache is good for Phoenix, a
virtuous cycle!

On Thursday, December 5, 2013, Stack wrote:

> Discussion of the Phoenix proposal has settled since its original
> posting on November 7th.  Feedback has been incorporated.
> Let us now move to a vote.
> Should Phoenix become an Apache incubator project?
> [] +1 Accept Phoenix into the Incubator
> [] +0 Don't care whether or which
> [] -1 Do not accept Phoenix into the Incubator because...
> The latest version of the proposal can be found here [1].  It is
> also posted below for your convenience.
> Let the vote run 72 hours.
> Thank you,
> St.Ack
> 1.
> Abstract
> Phoenix is an open source SQL query engine for Apache HBase, a NoSQL data
> store. It is accessed as a JDBC driver and enables querying and managing
> HBase tables using SQL.
> Proposal
> Phoenix is an open source SQL skin over HBase delivered as a
> client-embedded JDBC driver targeting low latency queries over HBase data.
> Phoenix takes your SQL query, compiles it into a series of HBase scans, and
> orchestrates the running of those scans to produce regular JDBC result
> sets. The table metadata is stored in an HBase table and versioned, such
> that snapshot queries over prior versions will automatically use the
> correct schema. Direct use of the HBase API, along with coprocessors and
> custom filters, results in performance on the order of milliseconds for
> small queries, or seconds for tens of millions of rows. Phoenix interfaces
> with both Pig and Map-reduce for the input and output of data.
> Background
> Phoenix initially started as an internal project at to
> efficiently analyze big data stored in HBase. It was open sourced on Github
> about a year ago in Jan 2013. Over time Phoenix, together with HBase as the
> storage tier, has begun to evolve into a general SQL database with support
> for metadata management, secondary indexes, joins, query optimization, and
> multi-tenancy. This is expected to continue as Phoenix implements a
> cost-based query optimizer and potentially transaction support, and
> surfaces new HBase security features such as encryption and cell-level
> security. Phoenix's developer community has also grown to include
> additional companies such as Intel, who have contributed join support to
> Phoenix, as well as Hortonworks, who are in the process of porting Phoenix
> to the 0.96 release of HBase.
> Rationale
> As usage and the number of contributors to Phoenix has grown, we have
> sought for a long-term home for the project, and we believe the Apache
> foundation would be a great fit. Joining Apache would ensure that tried and
> true processes and procedures are in place for the growing number of
> organizations interested in contributing to Phoenix. Phoenix is also a good
> fit for the Apache foundation: Phoenix already interoperates with several
> existing Apache projects (HBase, Hadoop, Pig, BigTop). The Phoenix team is
> familiar with the Apache process and and believes in the Apache mission -
> the team already includes multiple Apache committers.
> Initial Goals
> The initial goals will be to move the existing codebase to Apache and
> integrate with the Apache development process. Once this is accomplished,
> we plan for incremental development and releases that follow the Apache
> guidelines.
> Current Status
> Phoenix has undergone two major and three minor releases (1.0, 1.1, 1.2,
> 2.0, and 2.1) as well as many patch releases. Phoenix is being used in
> production by as well as at other organizations. The Phoenix
> codebase is currently hosted at, which will form the basis of
> the Apache git repository.
> Meritocracy
> The Phoenix project already operates on meritocratic principles. Phoenix
> has several developers from various organizations outside of
> who have contributed major new features. While this process has remained
> mostly informal, as we do not have an official committer list, an implicit
> organization exists in which individuals who contribute major components
> act as maintainers for those modules. If accepted, the Phoenix project
> would include several of these participants as initial committers. We will
> work to identify all committers and PPMC members for the project and to
> operate under the ASF meritocratic principles.
> Community
> Acceptance into the Apache foundation would bolster the already strong user
> and developer community around Phoenix. That community includes many
> contributors from various other companies, and

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