incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Incubator Wiki] Update of "PhoenixProposal" by James.Taylor
Date Wed, 04 Dec 2013 17:58:53 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The "PhoenixProposal" page has been changed by James.Taylor:
https://wiki.apache.org/incubator/PhoenixProposal?action=diff&rev1=5&rev2=6

  Phoenix initially started as an internal project at Salesforce.com 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). The Phoenix team is familiar with the Apache process and and believes in the
Apache mission - the team already includes multiple Apache committers.
+ 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.
@@ -25, +25 @@

  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 an active mailing list composed of hundreds of users.
  
  === Core Developers ===
- The core developers of our project are listed in our contributors and initial PPMC below.
Though many are employed at Salesforce.com, there is a representative cross sampling of other
organizations including Intel, Hortonworks, Cloudera, and Twitter.
+ The core developers of our project are listed in our contributors and initial PPMC below.
Though many are employed at Salesforce.com, there is a representative cross sampling of other
organizations including Intel, Hortonworks, and Cloudera.
  
  === Alignment ===
  Our proposed Phoenix effort aligns closely with Apache HBase. The HBase project perimeter
is denoted by a simple byte-array based Create, Read, Update, Delete and Scan APIs with no
current plans to extend beyond this bounds. Phoenix complements this with a higher level API
in SQL with which many are already familiar. At first glance, it may seem that Phoenix should
just be folded into HBase as a new module. However, the focus of the two projects will be
quite different, especially as Phoenix matures. With secondary indexing and joins just having
been introduced into Phoenix, the next big frontier will be to implement a cost-based query
optimizer. This is the heart-and-soul of most relational databases and can can take a lifetime
to get right.
@@ -48, +48 @@

  Phoenix has existed as a healthy open source project for almost a year. During that time,
James, Mujtaba, and others have successfully fostered an open-source community, attracting
users and developers from a diverse group of companies including Intel, Intuit, Bloomberg,
Tagged, and Hortonworks. Although neither are committers on other Apache projects, both James
and Mujtaba have experience working with and contributing to other Apache projects.
  
  === Homogenous Developers ===
- The initial list of committers includes developers from several institutions, including
Salesforce, Intel, Hortonworks, and Twitter.
+ The initial list of committers includes developers from several institutions, including
Salesforce, Intel, and Hortonworks.
  
  === Reliance on Salaried Developers ===
  Like most open source projects, Phoenix receives substantial support from salaried developers.
A large fraction of Phoenix development is supported by Salesforce.com. In addition, those
working from within corporations and universities often devote “after hours” or spare
time to the project. We will continue our efforts to ensure stewardship of the project to
be independent of salaried developers.
@@ -124, +124 @@

   * Ramkrishna S Vasudevan <ramkrishna at apache dot org>
   * Jeffrey Zhong <jeffreyz at apache dot org>
   * Nick Dimiduk <ndimiduk at apache dot org>
-  * Tony Huang <thuang at twitter dot com>
  
  == Affiliations ==
- The initial committers are from four organizations: Salesforce.com, Intel, Hortonworks,
and Twitter.
+ The initial committers are from three organizations: Salesforce.com, Intel, and Hortonworks.
  
   * James Taylor (Salesforce.com)
   * Mujtaba Chohan (Salesforce.com)
@@ -139, +138 @@

   * Ramkrishna S Vasudevan (Intel)
   * Jeffrey Zhong (Hortonworks)
   * Nick Dimiduk (Hortonworks)
-  * Tony Huang (Twitter)
  
  == Sponsors ==
  === Champion ===

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message