What the board has decided about this committee or office, and the reports it filed, most recent first. Generated from the published minutes.
These categorised views are best effort. They are read from the published minutes by a program, and what it can attribute to a committee depends on how each resolution happens to be worded — so a page may be incomplete, and nothing here overrides the minutes themselves. The raw minutes are the source of truth.
Please note. The board approves the minutes of a meeting at the meeting after it, and they are published then - so the most recent meeting is not usually here. ASF Members can read the draft in the board's own repository until it is.
[raw] the published minutes, which are the record. [main index]
| Date | Action | Decided by |
|---|---|---|
| 2026-06-17 | Appointed Viraj Jasani | the board, by resolution |
| 2024-10-16 | Appointed Istvan Toth | the board, by resolution |
| 2022-05-18 | Appointed Rajeshbabu Chintaguntla | the board, by resolution |
| 2020-04-15 | Appointed Ankit Singhal | the board, by resolution |
| 2018-03-21 | Appointed Josh Elser | the board, by resolution |
| 2014-05-21 | Appointed James R. Taylor | the board, by resolution |
| Date | Decision | Item | Outcome |
|---|---|---|---|
| 2014-05-21 | Establish the Apache Phoenix Project | special order | approved |
## Description: The mission of Phoenix is the creation and maintenance of software related to High performance relational database layer over Apache HBase for low latency applications ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Phoenix was founded 2014-05-20 (12 years ago) There are currently 60 committers and 39 PMC members in this project. The Committer-to-PMC ratio is roughly 5:4. Community changes, past quarter: - Lokesh Khurana was added to the PMC on 2026-08-02 - Palash Chauhan was added to the PMC on 2026-06-02 - No new committers. Last addition was Nihal Jain on 2025-08-05. ## Project Activity: Development activity remains average. Feature development is concentrated on the consistent HA failover feature, improving CDC and eventually consistent GSIs, as well as support for the Phoenix DynamoDB adapter. Lots of efforts to improve the flaky tests, and critical bug fixes are in progress. Recent releases: 5.2.2 was released on 2026-07-04. 5.3.2 was released on 2026-07-04. 5.3.1 was released on 2026-05-18. ## Community Health: Overall community health is acceptable. Most of the development is done by our core team of about a dozen active developers.
## Description: The mission of Phoenix is the creation and maintenance of software related to High performance relational database layer over Apache HBase for low latency applications ## Project Status: Current project status: Ongoing Issues for the board: Our former Chair, Istvan Toth, stepped down for health reasons. We are saddened to report his recent passing, after a brief illness. A VOTE for new PMC chair was completed, proposing Viraj Jasani (vjasani) be appointed to the position of VP, Apache Phoenix. The vote passed with 11 +1 binding votes and no vetos: https://lists.apache.org/thread/dn9gd8ncpxkj5t457gbct7655xnp78sk Phoenix 5.3.1 release is in progress. We expect to complete the release before the end of the month. ## Membership Data: Apache Phoenix was founded 2014-05-20 (12 years ago) There are currently 60 committers and 38 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past quarter: - No new PMC members. Last addition was Jacob Isaac on 2023-11-06. - No new committers. Last addition was Nihal Jain on 2025-08-05. ## Project Activity: Development activity remains average. Feature development is concentrated on the consistent failover feature, improving CDC (Change Data Capture), and support for the DynamoDB connector/adapter. Recent major features also include the eventually consistent global secondary indexes. Some recent enhancements include new metrics at client and server side. Recent releases: thirdparty-2.2.0 was released on 2025-12-10. 5.3.0 was released on 2025-10-03. phoenix-omid-1.1.3 was released on 2025-04-04. 87 JIRA tickets were opened and 56 were closed in the past quarter. dev@phoenix.apache.org had a 100% increase in traffic in the past quarter (338 emails compared to 169) issues@phoenix.apache.org had a 79% increase in traffic in the past quarter (542 emails compared to 302) ## Community Health: Overall community health is acceptable. Most of the development is done by our core team of about a dozen active developers.
## Description: The mission of Phoenix is the creation and maintenance of software related to High performance relational database layer over Apache HBase for low latency applications ## Project Status: Current project status: Ongoing Issues for the board: Our current Chair, Istvan Toth, has stepped down effective immediately for health reasons. Istvan nominated a successor. The Phoenix PMC will run a vote for a new PMCC as soon as possible. ## Membership Data: Apache Phoenix was founded 2014-05-21 (11 years ago) There are currently 61 committers and 38 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past quarter: - No new PMC members. Last addition was Jacob Isaac on 2023-11-07. - Nihal Jain was added as committer on 2025-08-05 ## Project Activity: Development activity remains average. Feature development is concentrated on the consistent failover feature, improving CDC (Change Data Capture), and support for the DynamoDB connector. Recent releases: thirdparty-2.2.0 was released on 2025-12-10. 5.3.0 was released on 2025-10-03. 37 JIRA tickets were opened and 30 were closed in the past quarter. dev@phoenix.apache.org had a 28% decrease in traffic in the past quarter (185 emails compared to 254), likely attributable to the holiday season. The customary notable changes list will not appear in this report but will be returning soon. ## Community Health: Overall community health is good. Most of the development is still done by our core team of about a dozen active developers.
## Description: The mission of Phoenix is the creation and maintenance of software related to High performance relational database layer over Apache HBase for low latency applications ## Project Status: Current project status: Ongoing Issues for the board: No issues to report to the board at this time. ## Membership Data: Apache Phoenix was founded 2014-05-21 (11 years ago) There are currently 61 committers and 38 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past quarter: - No new PMC members. Last addition was Jacob Isaac on 2023-11-07. - Nihal Jain was added as committer on 2025-08-05 ## Project Activity: Development activity was lower in this quarter as most activity was concentrated on finalizing features for the 5.3.0 release and bug fixes. The project has released Phoenix 5.3.0 which added JSON and BSON data types and CDC (Change Data Capture) capabilities, as well as improvements to the High Availability and Time To Live features. We are in the process of adding a new sub-project that provides an API compatible drop-in replacement for AWS DynamoDB using Phoenix. Notable changes and new features in the quarter (most included in 5.3.0): Dependency version updates: PHOENIX-7708 Update Jackson to 2.18.4.1 PHOENIX-7697 Update Gson to 2.13.1 PHOENIX-7698 Update Netty to 4.1.126 PHOENIX-7699 Update Jetty to 9.4.58.v20250814 PHOENIX-7696 Update Hadoop 3.4 version to 3.4.2 PHOENIX-7687 Wrong Hadoop version used for Hbase 2.5.0 profile CDC Feature related: PHOENIX-7718 : CDC Stream improvements BSON feature related: PHOENIX-7692: Path validations for bson update expression PHOENIX-7691 : Handle empty bson doc in bson update expression function HA feature related: PHOENIX-7695 : ParallelPhoenixResultSet keeps the unused result set open for too long PHOENIX-7426 Generating index mutations for immutable tables on the server side Other notable changes and fixes: PHOENIX-7370 Server to server system table RPC calls should use separate RPC handler pool PHOENIX-7711 Make Phoenix test jar available for consumption by applications PHOENIX-7709 Index committer post writer lazy mode - Async RPC call for verified index mutations PHOENIX-7707 Phoenix server paging on valid rows PHOENIX-7705 Support for a row size function PHOENIX-7582 Accept phoenix.skip.system.tables.existence.check from hbase-site.xml PHOENIX-7701 UngroupedAggregateRegionScanner doesn't release rpc handler on page timeouts PHOENIX-7702 Backward compatibility test framework support for phoenix 5.2 and hbase 2.6 PHOENIX-7700 Update default values for schema change retry policy PHOENIX-7638 Creating a large number of views leads to OS thread exhaustion PHOENIX-7690 Add a config to enable using bloom filters for multi-key point lookups PHOENIX-7651 Support RETURNING * with UPSERT and DELETE PHOENIX-7670 Region level threadpool for uncovered index to scan data table PHOENIX-7684 Introduce Segment Scan PHOENIX-7682 Review and simplify compatibility modules PHOENIX-7628 Don't add Apache Snapshot Maven Repo by Default ## Community Health: Overall community health is good. We have added a new committer in the quarter.
## Description: The mission of Phoenix is the creation and maintenance of software related to High performance relational database layer over Apache HBase for low latency applications ## Project Status: Current project status: Ongoing Issues for the board: No issues to report to the board at this time. ## Membership Data: Apache Phoenix was founded 2014-05-21 (11 years ago) There are currently 61 committers and 38 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past quarter: - No new PMC members. Last addition was Jacob Isaac on 2023-11-07. - Nihal Jain was added as committer on 2025-08-05 ## Project Activity: Development activity was average, feature development concentrated on improving CDC (Change Data Capture), TTL (Time to Live) and BSON support. Phoenix 5.3.0 is now considered feature complete, and we plan to release it in the next quarter. Phoenix 5.2.2 is still delayed due to lack of manpower to coordinate the release. Notable changes and new features in the quarter: Dependency version updates: PHOENIX-7683 Bump Apache Commons Lang 3 to 3.18.0 due to CVE-2025-48924 PHOENIX-7681 Update HBase 2.5 profile default version to 2.5.12 PHOENIX-7668 Update HBase 2.6 profile default version to 2.6.3 PHOENIX-7606 Remove HBase 2.4 support from master branch PHOENIX-7600 Replace commons-logging with slf4j HBase API usage updates in preparation for HBase 3.0: PHOENIX-7476 HBase 3 compatibility changes for Filters, ByteStringer, and Paging PHOENIX-7478 HBase 3 compatibility changes: Replace ClusterConnection with Connection API PHOENIX-7481 HBase 3 compatibility changes: Cleanup deprecated APIs, HTable and HTableDescriptor PHOENIX-7505 HBase 3 compatibility changes: Update zookeeper handling Reformatting the codebase with Spotless: PHOENIX-7676 Update checkstyle checker.xml based on spotless rules PHOENIX-7443 Add Spotless to the pre-commit checks PHOENIX-7442 Apply Spotless to reformat the entire codebase PHOENIX-7675 Update spotless plugin to also format IT classes PHOENIX-7441 Integrate the Spotless plugin and update the code template CDC Feature related: PHOENIX-7677 TTL_DELETE CDC event to use batch mutation PHOENIX-7671 Fix CDCStreamIT for HBase 2.6 PHOENIX-7664 Remove EmptyColumnOnlyFilter and FirstKeyOnlyFilter for CDC scanners PHOENIX-7658 CDC event for TTL_DELETE to exclude pre-image if PRE scope is not selected PHOENIX-7584 Conditional TTL on SYSTEM.CDC_STREAM PHOENIX-7653 New CDC Event for TTL expired rows PHOENIX-7652 : Clear CDC Stream metadata when table is dropped PHOENIX-7643 : Add parent partition start time to CDC_STREAM table PHOENIX-7636 CDC on table with case-sensitive pk columns fails to read change records PHOENIX-7634 : Change stream name delimiter PHOENIX-7609 : CDC creation fails when data table has case sensitive name TTL feature related: PHOENIX-7677 TTL_DELETE CDC event to use batch mutation PHOENIX-7661 Clean up old framework for TTL masking and expiration PHOENIX-7674 Fix Bson3IT for HBase 2.6 PHOENIX-7667 Strict vs Relaxed TTL BSON feature related: PHOENIX-7551 BSON_VALUE_TYPE function to return the data type of BSON field value PHOENIX-7673 BSON Condition Function size() PHOENIX-7663 : BSON Condition Function field_type() PHOENIX-7674 Fix Bson3IT for HBase 2.6 PHOENIX-7662 BSON Condition Function contains() PHOENIX-7545 BSON_VALUE() to support returning sub-document PHOENIX-7585 New BSON Condition Function begins_with() PHOENIX-7654 Restrict BSON datatype in composite PK as last part of the pk column PHOENIX-7650 Default value support in BSON_VALUE() for all supported types PHOENIX-7647 : BSON_UPDATE_EXPRESSION() set value if field key does not exist PHOENIX-7641 Support placeholder for document field keys in BSON condition expression PHOENIX-7631 BSON_VALUE() to support returning binary value with VARBINARY_ENCODED data type PHOENIX-7617 BSON serialization should retain ByteBuffer offset Other notable changes: PHOENIX-7659: Leverage = ANY() instead of big IN list to do huge number of point lookups in a single query PHOENIX-7612 Fix Cell references in IndexRegionObserver PHOENIX-7666 Index query failure with SkipScanFilter PHOENIX-7671 Sync maxLookback from data table to indexes PHOENIX-7626: Add metrics to capture HTable thread pool utilization and contention PHOENIX-7648 Introduce new Atomic Operation - ON DUPLICATE KEY UPDATE_ONLY PHOENIX-7645 HighAvailabilityGroup can leak zookeeper connections PHOENIX-7646 New PhoenixStatement API to return old row state in Atomic Updates PHOENIX-7630: Return ResultSet for UPSERT with ON DUPLICATE KEY PHOENIX-7639 Improve error handling in PhoenixMasterObserver PHOENIX-7619 Excess HFiles are being read to look for more than required column versions PHOENIX-7627 Atomic Delete return row fails for case-sensitive schema and table names PHOENIX-7358 Upsert select result wrong when use order by in query PHOENIX-7615: Fix NPE in handling NULL value PHOENIX-7616 NPE when there are Conditional expressions on indexed columns PHOENIX-7599: Fix count of rows scanned metric for uncovered indexes PHOENIX-7610 Using CAST() on pk columns always result in full table scan PHOENIX-7614 : Fix atmoic update return result with case sensitive table name PHOENIX-7605 Adding ability to configure threadpool at CQSI level PHOENIX-7608 : Partial index creation fails when creating it on a table with case sensitive table name PHOENIX-7586 :- Handle Role transitions for ActiveToStanby role in Failover HAPolicy ## Community Health: Overall community health is good. Most of the development is still done by our core team of about a dozen active developers.
## Description: The mission of Phoenix is the creation and maintenance of software related to High performance relational database layer over Apache HBase for low latency applications ## Project Status: Current project status: Ongoing Issues for the board: No issues to report to the board at this time. ## Membership Data: Apache Phoenix was founded 2014-05-21 (11 years ago) There are currently 60 committers and 38 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past quarter: - No new PMC members. Last addition was Jacob Isaac on 2023-11-07. - Hari Krishna Dara was added as committer on 2025-04-21 - Sanjeet Malhotra was added as committer on 2025-04-16 ## Project Activity: Apache Phoenix had its last main release 5.2.1 on 2024-11-12. The Apache Omid subproject has released version 1.1.3 on 2025-04-17 with new Hadoop and HBase versions, and multiple component version updates. Phoenix 5.2.2 release is still planned for the near future, and discussions about the 5.3.0 release have started. Notable changes and new features in the quarter: Dependency version updates: Updated default Hadoop version to 3.4.1. PHOENIX-7532 Update default Hbase 2.6 version to 2.6.2 PHOENIX-7539 Update default HBase 2.5 version to 2.5.11 PHOENIX-7572 Update OMID to 1.1.3 Other Component updates (mostly CVE) in preparation for the new release CDC related improvements: PHOENIX-7507 Update ROW_KEY_MATCHER column type to be VARBINARY_ENCODED PHOENIX-7499 : Update stream metadata when data table regions merge PHOENIX-7510 VARBINARY_ENCODED should support using hex format in WHERE... PHOENIX-7499 : Update stream metadata when data table regions PHOENIX-7518 Fix Flapper test in CDCQueryIT HA related improvements: PHOENIX-7493 Graceful Failover with Phoenix HA PHOENIX-7502 :- Decouple principal from HAGroupInfo PHOENIX-7495 :- Support for HBase Registry Implementations in Phoenix... Other new features: PHOENIX-7107 Add support for indexing on SYSTEM.CATALOG table PHOENIX-7515: Add metric for count of Phoenix client batches used by ... PHOENIX-7463 New ANTLR grammar to evaluate BSON's SQL styleexpressions PHOENIX-7186 Support Square Brackets Notation for IPv6 in JDBC URL PHOENIX-7170 Conditional TTL As well as more than a dozen dozen other bug fixes, test fixes and improvements and build/CI system fixes. ## Community Health:, Overall community health is good. We have released a new Omid version and are preparing for the 5.3.0 and 5.2.2 releases. Most of the development is still done by our core team of about a dozen active developers. Activity in February was low, but has picked up in March and April, especially in the Omid subproject, related to the new release.
## Description: The mission of Phoenix is the creation and maintenance of software related to High performance relational database layer over Apache HBase for low latency applications ## Project Status: Current project status: Ongoing Issues for the board: No issues to report to the board at this time. ## Membership Data: Apache Phoenix was founded 2014-05-21 (11 years ago) There are currently 58 committers and 38 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past quarter: - No new PMC members. Last addition was Jacob Isaac on 2023-11-07. - No new committers. Last addition was Palash Chauhan on 2024-06-11. ## Project Activity: Apache Phoenix had its last main release 5.2.1 on 2024-11-12. 5.2.2 release is planned for early spring, pending the release of HBase 2.6.2 and 2.5.11 which will significantly reduce our transitive CVE exposure. In the past quarter: * Landed several improvements to the Change Data Capture feature: * PHOENIX-7500 Add PARENT_PARTITION_ID to SYSTEM.CDC_STREAM table's composite pk * PHOENIX-7473 Eliminating index maintenance for CDC index * PHOENIX-7469 Partitioned CDC Index for partitioned tables * PHOENIX-7460 Update stream metadata when a data table region splits * PHOENIX-7459 Bootstrap stream metadata when CDC is enabled/created on a table * PHOENIX-7458 Create new SYSTEM tables for tracking CDC Stream metadata * PHOENIX-7425 Partitioned CDC Index for eliminating salting * Landed some other notable new features * PHOENIX-7434 Extend atomic support to single row delete with condition on non-pk columns * PHOENIX-7462 Single row Atomic Upsert/Delete returning result should return ResultSet * PHOENIX-7424 Support toStringBinary/toBytesBinary conversion * About a dozen other commits: smaller features, bugfixes, build and dependency changes ## Community Health: Overall community health is good. We have released a new maitenance release, and major feature work continues on the CDC feature. Most of the development is still done by our core team of about a dozen active developers. Activity has decreased this quarter, some of which is due to the festive season and the increased activity related to the 5.2.1 release at the end of the last quarter.
## Description: The mission of Phoenix is the creation and maintenance of software related to High performance relational database layer over Apache HBase for low latency applications ## Project Status: Current project status: Ongoing Issues for the board: No issues to report to the board at this time. ## Membership Data: Apache Phoenix was founded 2014-05-21 (10 years ago) There are currently 58 committers and 38 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past quarter: - No new PMC members. Last addition was Jacob Isaac on 2023-11-07. - No new committers. Last addition was Palash Chauhan on 2024-06-11. ## Project Activity: Apache Phoenix had its last main release 5.2.0 on 2024-04-16. Python Driver for Apache Phoenix (phoenixdb) 1.2.2 released on 7th June 2024. Relese process for Apache Phoenix 5.2.1 is ongoing. In the past quarter: * Landed the following significant new features: * PHOENIX-7330 Introducing Binary JSON (BSON) with Complex Document structures in Phoenix * PHOENIX-7357 New variable length binary data type: VARBINARY_ENCODED * PHOENIX-7398 New PhoenixStatement API to return row for Atomic/Conditional Upserts * PHOENIX-7411 Atomic Delete: PhoenixStatement API to return row if single row is atomically deleted (#1985) * PHOENIX-7343: Support ARRAY and JSON as simple values in CDC * PHOENIX-6940 Add a connector variant for Hive 4 * PHOENIX-6783 Add spark-sql support for spark2 datasourceV2 and spark3 * Fixed more than a dozen bugs, and added several minor features and refactors. * Performed routine and CVE related component upgrades * Worked on compatibility issues with JDK23 and HBase 2.6.1 ## Community Health: Overall community health is good. We have landed several new features, some of which were started well before this quarter. We have received valuabale contributions from a new contributor to the Spark connector. We have worked with the Trino community to address their security concerns, and with the HBase project on API compatibility issues. Most of the development is done by our core team of about a dozen active developers, but we do receive outside contributions and some new developers are getting up to speed with the project. After a lull in the previous quarter, activity is close to the average of the last few years for the quarter.
## Description: The mission of Phoenix is the creation and maintenance of software related to High performance relational database layer over Apache HBase for low latency applications and operational analytical workloads. ## Project Status: Current project status: HEALTHY Issues for the board: No issues to report to the board at this time. ## Membership Data: Apache Phoenix was founded 2014-05-21 (10 years ago) There are currently 58 committers and 38 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past quarter: - No new PMC members. Last addition was Jacob Isaac on 2023-11-07. - Palash Chauhan was added as committer on 2024-06-12 ## Project Activity: Apache Phoenix had its last main release 5.2.0 on 2024-04-16. Python Driver for Apache Phoenix (phoenixdb) 1.2.2 released on 7th June 2024. Planning to release 5.2.1 soon. In the past quarter - Extensive work has been done to complete the follow features: a. Native JSON data type and Binary JSON (BSON) with Complex Document structures b. Support HBase 2.6 c. Leverage bloom filters for multi-key point lookups d. Redesign of Phoenix TTL for views - Fixed a good amount of performance issues around metadata cache, avoided unnecessary RPC calls and extensive locks wherever not required. Active development is going on in a. Change Data Capture(CDC) feature b. New variable length binary data type VARBINARY_ENCODED c. Hive 4 support in Phoenix-Connectors d. ested loop joins 5. Some more Performance improvements ## Community Health: The Phoenix community continues to remain active. There is a decrease in mail traffic of dev, JIRA and commit activities compared to last quarter because of focused development on high critical feature development and due to the holiday season.
## Description:
The mission of Phoenix is the creation and maintenance of software related to
High performance relational database layer over Apache HBase for low latency
applications
## Project Status:
Current project status: Super Healthy
Issues for the board:No issues to report to the board at this time.
## Membership Data:
Apache Phoenix was founded 2014-05-21 (10 years ago)
There are currently 57 committers and 38 PMC members in this project.
The Committer-to-PMC ratio is 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Jacob Isaac on 2023-11-07.
- No new committers. Last addition was Lokesh Khurana on 2024-01-16.
## Project Activity:
- Apache Phoenix had it's last main release 5.2.0 on 2024-04-16 which
improves stability and reliability.
- Phoenix Omid 1.1.2 released on 27th May 2024.
- Planning to release 5.1.4 and pythondb 1.2.2 in this month
- Voting is underway for the committer nomination
In the past quarter
- Fixed good amount of performance issues
- Dropped support of HBase 2.4.0 in 5.2.0 release.
- Bumped up Zookeeper and Avatica to latest stable releases.
- Active development is going in
1) Support native JSON data type which is near to completion.
2) Redesign of Metadata APIs
3) Change Data Capture(CDC) feature.
4) Support for HBase 2.6 and 3.0
## Community Health:
The Phoenix community continues to remain active.
There is an Increase in mail traffic for dev, decrease in the JIRA
and commit activities compared to last quarter because of focused
development on few big features.
- Mail Traffic:
1) Dev-related emails increased by 1%, from 683 to 690.
2) Issue-related emails decreased by 28% from 1664 to 1208
3) User-related emails are almost the same.
- JIRA Activity:
1) The number of issues opened(100) is decreased by 15%
2) The number of issues closed(52) is decreased by 49%
Code Contributors:
1) There were 18 code contributors: decreased by 38%.
## Description: The mission of Phoenix is the creation and maintenance of software related to High performance relational database layer over Apache HBase for low latency applications ## Project Status: Current project status: Super Healthy Issues for the board: No issues to report to the board at this time. ## Membership Data: Apache Phoenix was founded 2014-05-21 (10 years ago) There are currently 58 committers and 39 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past quarter: - No new PMC members. Last addition was Jacob Isaac on 2023-11-07. - Lokesh Khurana was added as committer on 2024-01-16 ## Project Activity: Apache Phoenix had its last main release 5.1.3 on 2022-12-30. Phoenix Thirdparty 2.1.0 released on 20th December 2023. Phoenix Omid 1.1.1 released on 8th February 2024. Planning to release 5.1.4 and 5.2.0 sooner in the next quarter. Active development is going on to release phoenix connectors 6.0.0. In the past quarter - Added support of partial indexes - Fixed critical data integrity issues - Separated phoenix-core into client, server modules. - Added support for JDK 17 for Phoenix and Omid. - Added TLS support in Omid. - Fixed good number of security issues. Active development is going in - Support native JSON data type. - Redesign of Metadata APIs - Change Data Capture(CDC) feature. - Support for HBase 2.6 and 3.0 ## Community Health: The Phoenix community continues to remain active. There is an Increase in mail traffic for dev and issues, decrease in the JIRA and commit activities compared to last quarter because of focused development on few features. Mail Traffic: - Dev-related emails increased by 20%, from 633 to 763. - Issue-related emails increased by 23%, from 1473 to 1823. - User-related emails decreased by 48%, from 22 to 11. JIRA Activity: - The number of issues opened decreased by 76%, from 30 to 7. - The number of issues closed decreased by 70%, from 28 to 8. Pull Requests: - The number of PRs opened decreased by 75%, from 26 to 6. - The number of PRs closed decreased by 70%, from 30 to 9. New Code Contributors: - There were 14 new code contributors added.
## Description:
The mission of Phoenix is the creation and maintenance of software related to
High performance relational database layer over Apache HBase for low latency
applications
## Project Status:
No issues to report to the board at this time.
## Membership Data:
Apache Phoenix was founded 2014-05-21 (9 years ago)
There are currently 57 committers and 39 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:4.
Community changes, past quarter:
- Jacob Isaac was added to the PMC on 2023-11-07
- Rushabh Shah was added as committer on 2023-08-15
## Project Activity:
Apache Phoenix had its last main release 5.1.3 on 2022-12-30.
No Releases given in the past quarter.
Discussion is ongoing to release Phoenix 5.1.4, Phoenix Omid 1.1.1
and Phoenix third party.
In the past quarter
1) Added support for multiple connection registries like master,
rpc and zookeeper in jdbc url
2) Removed the Kafka and Flume connectors support due to lack of
maintainers.
3) Discussions happened to replace the HTrace with OpenTelemetry
and other solutions to improve the query execution visibility.
4) Good number of security issues are fixed.
5) Active development is going in
- Partial index development
- Support native JSON data type.
- Redesign of Phoenix TTL for views
- Change Data Capture(CDC) feature.
- Replace hadoop and hbase clients with shaded hadoop
and hbase clients respectively.
## Community Health:
The Phoenix community continues to remain active.
Glad to see a huge increase in mail traffic, JIRA and
commit activities compared to last quarter.
1) Traffic :
dev - 647 emails compared to 300 (115%),
issues - 1484 emails compared to 1218(21%)
user - 22 emails compared to 6 (266%)
2) JIRA activity : 104 issues Opened(38%) and 66 issues Closed(26%)
3) Pull requests : 101 PRs Opened(57%) and 87 PRs Closed(-55%)
18 new code contributors were added
## Description: The mission of Phoenix is the creation and maintenance of software related to High performance relational database layer over Apache HBase for low latency applications ## Project Status: Current project status: Ongoing with high activity Issues for the board: No issues to report to the board at this time. ## Membership Data: Apache Phoenix was founded 2014-05-21 (9 years ago) There are currently 56 committers and 38 PMC members in this project. The Committer-to-PMC ratio is roughly 7:5. Community changes, past quarter: - No new PMC members. Last addition was Tanuj Khurana on 2023-01-02. - No new committers. Last addition was Tanuj Khurana on 2021-12-08. - Voting is underway for committer nomination. ## Project Activity: Apache Phoenix had its last main release 5.1.3 on 2022-12-30. No Releases given in the past quarter but planning to release Phoenix 5.2.0, query server 6.1.0 and Phoenix db 1.3.0 as well as phoenix-connectors. In the past quarter - Good number of security fixes are fixed. - Fixed issues with uncovered global indexes - Removed the connectors support for EOL Phoenix 4.x - Implemented applicable date/time features from JDBC 4.2 Active development is going in - Phoenix metadata caching - Improvements in cross cluster replication of phoenix tables. - Redesign of Phoenix TTL for views - Change Data Capture(CDC) feature. ## Community Health: Phoenix community continues to remain active, There is a decrease in mail traffic other than issues mailing list, JIRA activity and PRs compared to last quarter. 1) Traffic : dev(-18%) and issues(26%) 2) JIRA activity : Opened(-24%) and Closed(-30%) JIRAs 3) Pull requests : Opened(-12%) and Closed(171%) 13 new code contributors were added.
## Description: The mission of Phoenix is the creation and maintenance of software related to High performance relational database layer over Apache HBase for low latency applications ## Issues: No issues to report to the board at this time. ## Membership Data: Apache Phoenix was founded 2014-05-21 (9 years ago) There are currently 56 committers and 38 PMC members in this project. The Committer-to-PMC ratio is roughly 7:5. Community changes, past quarter: - No new PMC members. Last addition was Tanuj Khurana on 2023-01-02. - No new committers. Last addition was Tanuj Khurana on 2021-12-08. ## Project Activity: Apache Phoenix had its last main release 5.1.3 on 2022-12-30. No Releases given in the past quarter but active discussions going on to release Phoenix 5.2.0, query server 6.1.0 and Phoenix db 1.3.0 as well as phoenix-connectors. Dropped support of Pig in Phoenix Connector as there as no Pig releases in the last 6 years. Planning to drop support of Flume and Kafka connectors since the support was for the old version which has a lot of CVEs as well as no volunteers to support it, and lack of volunteers to update them. Dropped support of Phoenix 4.x as well HBase 2.3 for the upcoming Phoenix release, as HBase 2.3 is EOL. Development completed for Uncovered Global Indexes and Timezone sensitive date/time handling. Added TLS support in Omid. Active development is going in 1) Improve the performance of MR tools 2) Phoenix Metadata Caching. ## Community Health: Phoenix community continues to remain active, It's great that there is a huge increase in mail traffic, JIRA activity and PRs compared to last quarter. 1) Traffic : dev(67%) and issues(30%) 2) JIRA activity : Opened(60%) and Closed(50%) JIRAs 3) Pull requests : Opened(28%) and Closed(20%). 16 new code contributors were added.
## Description: The mission of Phoenix is the creation and maintenance of software related to High performance relational database layer over Apache HBase for low latency applications ## Issues: No issues to report to the board at this time. ## Membership Data: Apache Phoenix was founded 2014-05-21 (9 years ago) There are currently 56 committers and 38 PMC members in this project. The Committer-to-PMC ratio is roughly 7:5. Community changes, past quarter: - Tanuj Khurana was added to the PMC on 2023-01-02 - No new committers. Last addition was Tanuj Khurana on 2021-12-08. ## Project Activity: Apache Phoenix had its last main release 5.1.3 on 2022-12-30, with added HBase 2.5 support and notable features like Schema Tool improvements to get DDLs of tables, Client Side Metadata Caching Improvements, improved index usage in queries with uncovered columns along with some security fixes We are planning to release the next major release 5.2.0 soon. Removed Apache Tephra support from Phoenix. Active development is going on to support Uncovered Global Indexes and Timezone sensitive date/time handling and Sequences Performance Optimizations ## Community Health: Phoenix community continues to remain active, though sometimes most of the contributions and discussions come from a few individuals. Traffic on dev and user list declined from the last quarter by 24% and 12% respectively, and The same trend is seen for code commits, new JIRAs and PRs. though on a positive note 22 new contributors added.
## Description: The mission of Phoenix is the creation and maintenance of software related to High performance relational database layer over Apache HBase for low latency applications. ## Issues: No issues to report to the board at this time. ## Membership Data: Apache Phoenix was founded 2014-05-20 (8 years ago). There are currently 56 committers and 37 PMC members in this project. The Committer-to-PMC ratio is roughly 7:5. Community changes, past quarter: Richárd Antal was added to the PMC on 2022-09-28 No new committers. Last addition was Tanuj Khurana on 2021-12-08. ## Project Activity: Apache Phoenix had its last main release 5.1.2 on 2021-06-07, We are planning to release the next major release 5.2.0 soon. Discussion is going on to release 5.1.3 in a few days. We released python-phoenixdb 1.2.1 on 2022-10-25 with some fixes in the release and build scripts as well as an SPNEGO compatibility fix. We also released Phoenix Omid 1.1.0 on 2022-10-17 with changes to drop support for HBase 1.x, Kerberos fixes, dependency version updates etc. Completed Phoenix High Availability Feature which enables it to connect to a pair of HBase clusters to support disaster recovery. Discussion is going on to support a pluggable query logger and work is in progress for Phoenix Metadata caching improvements. Added support for Spark 3 in the Spark connector and significant improvements in Transform Tool. ## Community Health: Phoenix community continues to remain active, though sometimes most of the contributions and discussions come from a few individuals. The reporting tool complained about a -24% decline of dev traffic but the traffic of dev@(12%), commit@(18%) increased and user@, issues@ are almost the same compared with last quarter. We had a significant increase in closed PRs(52%). 19 code contributors (5% increase) added.
## Description: The mission of Phoenix is the creation and maintenance of software related to High performance relational database layer over Apache HBase for low latency applications. ## Issues: No issues to report to the board at this time. ## Membership Data: Apache Phoenix was founded 2014-05-20 (8 years ago). There are currently 56 committers and 36 PMC members in this project. The Committer-to-PMC ratio is roughly 7:5. Community changes, past quarter: Gokcen Iskender was added to the PMC on 2022-06-04. No new committers. Last addition was Tanuj Khurana on 2021-12-08. ## Project Activity: Apache Phoenix had its last main release 5.1.2 on 2021-06-07, We are planning to to release the next major release 5.2.0 soon after HBase 2.5 is released. We also released python-phoenixdb 1.2.0 on 2022-07-15 with some improvements and compatibility with the current python protobuf libraries. Active Development is going on Phoenix High Availability Feature which enables it to connect to a pair of HBase clusters supports disaster recovery. Development to migrate log4j to log4j2 is completed. Work to remove the Ttephra transactional system from Phoenix is going on as Tephra has old dependencies having high score CVEs and Apache attic libraries like Twill as there is no interest from the community to contribute to Tephra. Completed development of dropping support for HBase versions 2.1 and 2.2 from Apache Phoenix as they were already EOL'ed a long time back. ## Community Health: Phoenix community continues to remain active, though sometimes most of the contributions and discussions come from a few individuals. The reporting tool complaining about -24% decline of dev traffic but the traffic of user@, dev@ and @issues is slightly higher compare with last quarter as good amount discussion/reviews on the priority JIRAs/PRs related to new feature development of Phoenix High Availability, cleanup the EOL'ed HBase versions like 2.1,2,2 and 1.x and test case failures etc. We had a -61% decline in commit@ and closed PRs(-21%) in issues@phoenix.apache.org as the work is going on priority JIRAs/PRs.
## Description: The mission of Phoenix is the creation and maintenance of software related to High performance relational database layer over Apache HBase for low latency applications ## Issues: No issues to report to the board at this time. ## Membership Data: Apache Phoenix was founded 2014-05-20 (8 years ago) There are currently 56 committers and 35 PMC members in this project. The Committer-to-PMC ratio is 8:5. Community changes, past quarter: - No new PMC members. Last addition was Viraj Jasani on 2021-06-16. - No new committers. Last addition was Tanuj Khurana on 2021-12-07. ## Project Activity: Apache Phoenix had its last main release 5.1.2 on 2021-06-07, And we recently discussed cutting out another major release 5.2.0 soon. We dropped the support of HBase versions 2.1 and 2.2 from Apache Phoenix as they were already EOL'ed a long time back and also did not support our new implementation of global indexes, which are fully consistent. We also released phoenix-thirdparty 2.0.0 on 2022-04-19 to update the Guava and common-cli versions. We discussed removing HBase 1.x support from Apache Phoenix and Omid in subsequent releases. It will avoid backporting the fixes in multiple branches and maintaining shim layers. We recently discussed switching Phoenix on log4j2 from EOL'ed log4j1 and also to get compatible with Hbase 2.5, which supports log4j2 only. ## Community Health: Phoenix community continues to remain active, though sometimes most of the contributions and discussions come from a few individuals. There is a decline in traffic on user@ by 12%. Some of the discussions on the user@ list could get offset by the new users who are not aware of the mailing list and approaching other community sites supported by Vendors or other question/answer websites. We had a -24% decline in dev@ and -42% in issues@phoenix.apache.org due to less discussion/reviews on the JIRAs/PRs owing to more minor fixes than significant feature development in the last quarter. We did more commits(+53%) and closed more PRs(+5%) with 8% increase in code contributors.
## Description: The mission of Phoenix is the creation and maintenance of software related to High performance relational database layer over Apache HBase for low latency applications ## Issues: No issues to report to the board at this time. ## Membership Data: Apache Phoenix was founded 2014-05-20 (8 years ago) There are currently 56 committers and 35 PMC members in this project. The Committer-to-PMC ratio is 8:5. Community changes, past quarter: - No new PMC members. Last addition was Viraj Jasani on 2021-06-16. - Tanuj Khurana was added as committer on 2021-12-07 ## Project Activity: Apache Phoenix had its last release 5.1.2 on 2021-06-07, And we are dedicatedly making progress for our next releases 5.1.3 and 4.16.2 None of our released artifacts were affected by the recent severe log4j2 vulnerability(CVE-2021-44228) as we were using log4j1 in all our repositories except one where we had log4j2 as test dependency for phoenix-hive connector but it has also been taken care of. However, this reminded us that there are still a few critical vulnerabilities with our current log4j1 and we are in process of replacing it with "reload4j" to fix a few of the urgent CVEs. Though the long term plan is to eventually move on to the latest version We will be releasing Phoenix-thirdparty soon to bump the commons-cli and Guava version We reached the consensus of dropping the support of Apache Tephra(a podling adopted 2 years ago ) from Phoenix due to a lack of interest from the community to maintain it. We are seeing interest and receiving code contributions to support spark3 for Phoenix-connector. ## Community Health: The community activities had been declining for the last 3 quarters after our major release 5.1.0, as more efforts are spent on stabilizing the releases, rather than taking up major features. Traffic on dev and user list continues to decline from the last few quarters by 24% and 12% respectively, and the same trend is seen for code commits and new JIRAs. though on a positive note we closed more JIRAs then we opened this quarter and we have a steady rate of code contributors
## Description: The mission of Phoenix is the creation and maintenance of software related to High-performance relational database layer over Apache HBase for low latency applications ## Issues: No issues to rt to the board at this time. ## Membership Data: Apache Phoenix was founded 2014-05-20 (7 years ago) There are currently 55 committers and 35 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. Last addition was Viraj Jasani on 2021-06-16. - No new committers. Last addition was Jacob Isaac on 2021-05-28. ## Project Activity: * Apache Phoenix had its last release 5.1.2 on 2021-06-07, And we are in process of preparing release candidates for 5.1.3 and 4.16.2 which will have fixes for around 45+ issues. * We have released the Python PhoenixDb-1.1.0 on 2021-08-27, which introduces new APIs to access metadata for primary key and indices and improve our ORM support. * HBase 1.3 support has been dropped from Phoenix as this version was already EOL'ed by the HBase community on 2020-08-23. This will also help us in reducing our efforts in maintaining its compatibility module for every change. * Phoenix Tech Talk event held on 2021-10-07 detailing the process on how to change data format online without service disruption. ## Community Health: The community activities had declined in the last 2 quarters after the major release of 5.1.0, as we continue to focus on stabilization with maintenance releases rather than taking up the mega features. Traffic on dev list is reduced by 54% ,the number of Commits had declined by 36% and PRs by 14% as compared to last quarter, we closed only 47(40% less) JIRAs with 14 code contributors (56% less). Though, we see a slight increase(5%) in traffic on the user list. We also recognize that there is no PMC and committer added in the last 5 months. Hence, we will take this as an action item and evaluate the new contributors more frequently.
## Description: The mission of Phoenix is the creation and maintenance of software related to High performance relational database layer over Apache HBase for low latency applications ## Issues: No issues to report to the board at this time. ## Membership Data: Apache Phoenix was founded 2014-05-20 (7 years ago) There are currently 55 committers and 35 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - Viraj Jasani was added to the PMC on 2021-06-16 - Jacob Isaac was added as committer on 2021-05-28 ## Project Activity: * Apache Phoenix had its last release 5.1.2 on 2021-06-07 with 32 fixes, And another patch release 4.16.1 (on 2021-05-21) in the last quarter * Phoenix query server 6.0.0 was released on 2021-08-03 with improved authentication support and lightweight artifacts. * Phoenix tephra 0.16.1 was released on 2021-05-13 to support HBase 2.4. * Python PhoenixDb 1.1.0 release planning is in progress which will provide better ORM support with APIs to access metadata for primary key and indices. * Phoenix Tech Talk event held on 2021-07-01 to share how to achieve additional availability for Phoenix queries with multiple clusters. * Discussion on dropping support for EOL HBase 1.x didn't reach to consensus because of less participation from the community though the discussion is expected to be revived soon. ## Community Health: * The community activities had reduced from the last quarter owing to more work on stabilization of the releases than many new features. * Traffic on dev list was almost steady the but the number of Commits had declined by 21% and PRs by 35% but we manage to reduce some backlog by closing more JIRAs than we opened(70/59) with 28% more contributors
## Description: The mission of Phoenix is the creation and maintenance of software related to High performance relational database layer over Apache HBase for low latency applications ## Issues: No issues to report to the board at this time. ## Membership Data: Apache Phoenix was founded 2014-05-21 (7 years ago) There are currently 54 committers and 34 PMC members in this project. The Committer-to-PMC ratio is roughly 7:5. Community changes, past quarter: - Xinyi Yan was added to the PMC on 2021-03-31 - No new committers. Last addition was Viraj Jasani on 2021-02-06. ## Project Activity: * Apache Phoenix had its last release 5.1.1 on 2021-03-25, And two other key releases 5.1.0 (on 2021-02-10) and 4.16.0(on 2021-02-24) in the last quarter * There is a growing consensus on dropping support for EOL HBase 1.x runtime which will save some developer's efforts on backporting features to multiple branches that are based on different HBase and Java runtime. * Discussion on splitting our core module into server and client module to avoid conflicting with the libraries in runtimes that are not consistent at server and client. * Working on patch release to fix some nitty bugs of 4.16.0. * Total of 3 Phoenix Tech Talk events were held in the last quarter, we extend our thanks to all who have sincerely arranged the event and actively participated in the talks. ## Community Health: * Community activities got cool down after the enormous work done initially for the two major releases. * There is an increase in traffic on the user mailing list(+225%) owing some to tech talk discussions but traffic on the dev/issues mailing list(-50%) and the number of PRs/commit(-50%) has declined in this quarter as compared to our previous busy quarter * we closed/reviewed almost all the PRs opened(96/102)
## Description: The mission of Phoenix is the creation and maintenance of software related to High performance relational database layer over Apache HBase for low latency applications ## Issues: No issues to report to the board at this time. ## Membership Data: Apache Phoenix was founded 2014-05-20 (7 years ago) There are currently 54 committers and 33 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. Last addition was Istvan Toth on 2020-07-06. - Daniel Wong was added as committer on 2021-01-08 - Richárd Antal was added as committer on 2020-12-24 - Viraj Jasani was added as committer on 2021-02-05 ## Project Activity: Apache Phoenix had its last release of 4.15.0 on 2019-12-20. And, now the RCs of our mainstream branches 4.16.0 and 5.1.0 is up for the voting. Which will support Apache HBase versions 1.3, 1.4, 1.5, 1.6, 2.1, 2.2, 2.3, and 2.4. we released phoenix-thirdpary-1.1.0 on 2021-02-01 and, also made the first release of Apache Omid 1.0.2 on 2020-11-23 and Apache Tephra 0.16.0 on 2020-12-03 after their adoption in Phoenix. We are discussing having Phoenix Tech talks/meetup every month to share knowledge and discuss new ideas within the community for improvement and growth. Discussion on dropping the support of EOLs Apache HBase versions (1.3, 1.4, 2.1) in the next release, to reduce efforts on maintenance of multiple compatibility modules and save build/infrastructure time as well. Due to the lack of community support on nurturing Phoenix connectors for PIG and Flume and without exhaustive testing before release, we are considering marking them as unmaintained in the upcoming phoenix release. ## Community Health: Phoenix community continues to remain engaged with multiple releases and code contributions. We had closed more PRs/JIRAs than we opened, our commit activity had also improved, and there were 44% more code contributors than the previous quarter. Our interactions on the user list steadily declining QoQ, though we saw substantial growth in the traffic on issues(+100%) and dev list(+23%) in the last quarter.
## Description: The mission of Phoenix is the creation and maintenance of software related to High performance relational database layer over Apache HBase for low latency applications ## Issues: No issues to report to the board at this time. ## Membership Data: Apache Phoenix was founded 2014-05-20 (6 years ago) There are currently 51 committers and 33 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. Last addition was Istvan Toth on 2020-07-06. - No new committers. Last addition was Gokcen Iskender on 2020-02-07. ## Project Activity: Apache Phoenix had its last release of 4.15.0 on 2019-12-20. And, we were able to resolve maximum blockers for our next 4.16.0 and 5.1.0 releases but there are still some dependencies on the release of other projects. We are actively working towards it and expecting an RC soon. Thanks to RMs of these branches who are diligently tracking the progress. We had our very first major release of PhoenixDB 1.0.0 on 2020-09-18. It's our native Python driver for accessing Phoenix via query server. Phoenix-thirdparty 1.0.0 was released on 2020-10-26 to encapsulate Guava library in Phoenix. It was done to avoid conflict with the incompatible versions present in different Hadoop runtime for Phoenix. We are also working towards the first time release of Omid and Tephra after the adoption of these projects under the Apache Phoenix PMC. Build jobs were migrated on new Cloudbees infra and started using Yetus to validate new contributions. we appreciate the committers who worked on it. ## Community Health: We observe a steady flow of issues being created and resolved, and interactions continue to be active on mailing lists and PRs. The trend of traffic on the user list continue to decline QoQ from the last few years, though more activity is observed on our dev list this quarter. Even though the number of active contributors has declined by 23%, we were able to resolve 7% more issues from last quarter and our average resolution time has also improved by 32%. PMC has not received any nomination in the last quarter for the new committers or PMCs, however, we should take this as an action item again and evaluate contributors more frequently.
## Description: The mission of Phoenix is the creation and maintenance of software related to High performance relational database layer over Apache HBase for low latency applications ## Issues: No issues to report to the board at this time. ## Membership Data: Apache Phoenix was founded 2014-05-20 (6 years ago) There are currently 51 committers and 33 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - Istvan Toth was added to the PMC on 2020-07-06 - No new committers. Last addition was Gokcen Iskender on 2020-02-07. ## Project Activity: * Apache Phoenix had its last release of 4.15.0 on 2019-12-20. And, since then we have been actively working towards for our next 4.16.0 and 5.1.0 release. Current work is to bring some fixes in parity between both the release lines. * We are also figuring out a plan to do the release of adopted Apache projects(Omid, Tephra) and started preparing for the first release of our derived repos phoenix-connectors and phoenix-queryserver. * Phoenix PMC took over the ownership of pypi account of PhoenixDb and started preparing a release of our python-based phoenix driver for the first time after adopting PhoenixDb through code donation. * We had a discussion to make our binary release of 4.x branches on Java8 but had to defer it again, due to the dependency on HBase runtime which can still run on JDK 1.7. * To avoid conflict with guava version in a user runtime, a new repository phoenix-thirdparty was created to keep the shaded version of guava so that all downstream phoenix modules and public APIs can refer it consistently. * We also appreciate the committers who identified and fixed the time-consuming tests to improve our overall build efficiency so that new fixes can be verified faster and reduces some friction for the new contributors. ## Community Health: Phoenix continues to be an active and growing community. With new contributors and active committers, there is always a continuous flow of reviews and commits happening. We have not added any new committers in the last half year though as PMCs , we did evaluate few contributors but noone stand out at that time, but we will take this action item again and be more frequent in evaluating and nominating new contributors. There is a slight drop(-15%) of traffic on our dev mailing list from last quarter, though the traffic on user mailing list and number of active contributors are holding steady. We have seen an improvement in resolution time of issues in this quarter by 25% and our created-to-resolved ratio is still 4:3. I may be missing some statistics as community health metrics is not available(or not complete as it used to be) on the reporter tool so had to extract few of these manually.
## Description: The mission of Phoenix is the creation and maintenance of software related to High performance relational database layer over Apache HBase for low latency applications ## Issues: No issues to report to the board at this time. ## Membership Data: Apache Phoenix was founded 2014-05-20 (6 years ago) There are currently 51 committers and 32 PMC members in this project. The Committer-to-PMC ratio is roughly 7:4. Community changes, past quarter: - Ankit Singhal was appointed as a new PMC chair on 2020-04-15. - Kadir Ozdemir was added to the PMC on 2020-02-25 - No new committers. Last addition was Gokcen Iskender on 2020-02-07. ## Project Activity: - We had our last release of Phoenix 4.15.0 on 2019-12-20. Now, we have a RM for our next 4.16.0 release and there is also an active development going on our another parallel release line for 5.1.0 release. - All our connectors which are required by third party libraries to access Phoenix data are moved to a separate repo so that they can evolve with newer versions of these libraries and can be released independently. - I'm also happy to report that some committers had also taken up work to improve our build system, have put extra efforts in simplifying the code and consolidating branches to reduce friction for the new contributors. - we are also working towards bringing our python connector in parity with other connectors to accommodate non-java users who are more comfortable in writing applications in Python. ## Community Health: We have not added any new committers in the last quarter though as PMCs, we have taken this as an action item to continuously work towards evaluating and nominating new contributors. There is a consistent drop on our user mailing list year over year and this quarter we also observe a slight drop on our dev list . However, our number of active contributors have increased and issues created-to-resolved ratio has improved to 4:3.
## Description: The mission of Phoenix is the creation and maintenance of software related to High performance relational database layer over Apache HBase for low latency applications ## Issues: No issues to report to the board at this time. ## Membership Data: Apache Phoenix was founded 2014-05-20 (6 years ago) There are currently 51 committers and 31 PMC members in this project. The Committer-to-PMC ratio is roughly 7:4. Community changes, past quarter: - No new PMC members. Last addition was Chinmay Kulkarni on 2019-09-09. - Andreas Neumann was added as committer on 2019-12-03 - Terence Yim was added as committer on 2019-12-03 - Gokcen Iskender was added as committer on 2020-02-07 - Gokul Gunasekaran was added as committer on 2019-12-03 - Istvan Toth was added as committer on 2019-12-02 - Xinyi Yan was added as committer on 2019-12-26 - Yoni Gottesman was added as committer on 2019-12-03 ## Project Activity: Following up from the previous report, I'm happy to report that both the former podlings Omid and Tephra have been successfully "adopted" under the Apache Phoenix PMC. The PMC voted to grant committership to all PPMC who desired it, transitioned all infrastructure (e.g. Jira projects, Git repositories) under the Phoenix role, and did some basic updates to our public facing user-documentation to make sure our users can be aware of how these (now) sub-projects will continue to exist at the ASF. I'm also happy to report that Phoenix 4.15.0 was released in December. As is normal, we are also approaching a 4.15.1 bug-fix release in that release line. Activity on the 4.x release line continues at the usual cadence thanks to the dedicated work of the committers. On the 5.x release line, we were largely blocked because upstream Apache HBase changes caused us some API and runtime compatibility issues. Thankfully, after some more discussion on the matter, we got traction by a developer to chase down the problem and implement a solution. At this point, we are largely unblocked to work towards a long-overdue 5.1.0 release. ## Community Health: We've added 7 new committers since our last report which is fantastic. We have not, however, added any new committers. We should take this as an action item as a project. I find the mailing list traffic largely status quo; user lists have a drop year-over-year but the dev and issues list have an increase of a similar percentage magnitude year-over-year. In general, I observe a steady stream of user questions and developers created and resolving Jira issues.
## Description: The mission of Phoenix is the creation and maintenance of software related to High performance relational database layer over Apache HBase for low latency applications ## Issues: No issues for the board at this time. ## Membership Data: Apache Phoenix was founded 2014-05-20 (5 years ago) There are currently 44 committers and 31 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - Chinmay Kulkarni was added to the PMC on 2019-09-09 - No new committers. Last addition was Kadir Ozdemir on 2019-05-30. ## Project Activity: Business as usual for the community overall. We continue to have active development on the 4.x and 5.x release lines. There was an rc0 for a 4.15.0 release which is the next-up release to be had. The 5.x line still needs an owner to step up and drive a release cadence. There was a suggestion that the Omid and Tephra podlings graduate into sub-projects of the Apache Phoenix PMC. This suggestion was made as both Omid and Tephra have integration into Phoenix and provide some direct, end-user value. Both podlings were struggling to retain active podling memberships. The Phoenix community voted in favor of this graduation for both podlings, and all podling members who request it will be made Apache Phoenix committers. At this point, the 72hr lazy-consensus/notice on general@incubator to perform this double-podling subproject graduation has passed. VP-Phoenix and podling mentors need to sync and make a plan to start combining these resources. ## Community Health: Developer (dev/issues) mailing list traffic is down slightly, but user mailing list traffic is actually up over the past quarter. We continue to see an up-tick in the use of Github pull requests over patches on Jira (which may be related to the change in dev/issues traffic volume). As a project, continuing to ensure that Github-based code contributions are being integrated is ever more important. In general, we continue to see the same developers participating, with a reasonable number of new contributors to keep the committer pipeline active.
Omid is a flexible, reliable, high performant and scalable ACID transactional framework that allows client applications to execute transactions on top of MVCC key/value-based NoSQL datastores (currently Apache HBase) providing Snapshot Isolation guarantees on the accessed data. Omid has been incubating since 2016-03-28. ### Three most important unfinished issues to address before graduating: 1. Do podling name search. 2. 3. ### Are there any issues that the IPMC or ASF Board need to be aware of? N/A ### How has the community developed since the last report? N/A ### How has the project developed since the last report? N/A ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [ ] Community building - [X] Nearing graduation - [ ] Other: New important features focuses in production environments ### Date of last release: 2019-05-21 ### When were the last committers or PPMC members elected? 2018-09-25 ### Have your mentors been helpful and responsive? Our mentors were amazingly helpful, they help us finding performance and correctness bugs, as well as helped in the release process by evaluating the release and vote internally and externally. ### Comments Going forward, we need to document the additional features added for the integration with Apache Phoenix, as well as, the low latency algorithm. ### Signed-off-by: - [X] (omid) Alan Gates Comments: - [X] (omid) James Taylor Comments: - [ ] (omid) Lars Hofhansl Comments: ### IPMC/Shepherd notes: Justin Mclean: This report need more detail and tell us very little about the podlings progress. Pleas include more detail in you next report. I there any reason you have not added any committers/PPMC member for a year?
## Description: The mission of Phoenix is the creation and maintenance of software related to High performance relational database layer over Apache HBase for low latency applications ## Issues: No issues at this time! ## Membership Data: Apache Phoenix was founded 2014-05-20 (5 years ago) There are currently 44 committers and 30 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. Last addition was Chenglei on 2019-04-09. + New PMC member(s) under vote presently. - Kadir Ozdemir was added as committer on 2019-05-30 ## Project Activity: The community continues to have two active release lines: 4.x and 5.x. Since the last report, 4.14.2 was released and a 4.14.3 has its second release candidate out for a vote now. The 5.x release line has slowed since the initial 5.0.0 release. There was interest expressed in both 5.0 and 5.1 releases happening, but there is still significant progress required to get to a first release candidate for either. One impediment around the 4.x and 5.x release lines was ensuring that code changes make it to all relevant release branches. This continues to be an operational challenge for Phoenix as supporting a wide breadth of compatibility for Apache Hadoop and Apache HBase versions is challenging. This challenge is constantly being worked. For example, one community member took the time to re-vamp our automated testing on the ASF Jenkins which now shows largely passing test results, whereas the test results were essentially noise (no meaningful data could be parsed from the job output). On top of release stabilization, we can also be proud of a new significant feature (PHOENIX-5156 on ASF Jira) which took roughly 6 months to design, iterate, and commit. This is the hallmark of continuing innovation in Phoenix, rearchitecting one of the major enticing features of Phoenix to be more stable for our users. ## Community Health: Phoenix continues to be an active community with a strong core committership. Mailing list traffic, Jira issue activity, and commits are up (at least double-digit percents) over the last quarter. We did have a rather negative thread[1] on our user list since the last report in which a number of users expressed dissatisfaction with Phoenix. It is frustrating to have individuals come to your project's list, ultimately soliciting "what should I use instead?". Perhaps this is a good reminder to take a step back and make sure we are doing enough as a community to help make those who are not committers successful. However, as with all internet-based communities, I'm sure there are some hyper-critical individuals on our lists who aren't looking for a solution from Phoenix. [1] https://s.apache.org/44hy7
Omid is a flexible, reliable, high performant and scalable ACID transactional framework that allows client applications to execute transactions on top of MVCC key/value-based NoSQL datastores (currently Apache HBase) providing Snapshot Isolation guarantees on the accessed data. Omid has been incubating since 2016-03-28. ### Three most important unfinished issues to address before graduating: 1. Document additional features added for the integration with Apache Phoenix, as well as, the low latency algorithm. 2. Get positive feedback from other projects currently in Apache. 3. Do podling name search. ### Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? N/A ### How has the community developed since the last report? 1. Lars Hofhansl returned as a mentor. 2. A new release 1.0.1 was done that contains optimizations and bug fixes for the integration with Apache Phoenix. ### How has the project developed since the last report? Release 1.0.1 was published and includes optimization to Omid that inferred from the integration with Phoenix. These features mostly improve the performance of Omid, however, some are bug fixes that revealed by the integration with Phoenix while pushing Omid to its corner cases. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [ ] Community building - [x] Nearing graduation - [ ] Other: ### Date of last release: 2019-05-21 ### When were the last committers or PPMC members elected? 2018-09-25 ### Have your mentors been helpful? Our mentors were amazingly helpful, they help us finding performance and correctness bugs, as well as helped in the release process by evaluating the release and vote internally and externally. ### Signed-off-by: - [X] (omid) Alan Gates Comments: - [X] (omid) James Taylor Comments: - [ ] (omid) Lars Hofhansl Comments: ### IPMC/Shepherd notes:
Tephra is a system for providing globally consistent transactions on top of Apache HBase and other storage engines. Tephra has been incubating since 2016-03-07. ### Most important unfinished issues to address before graduating: 1. Improve community engagement 2. Increase adoption ### Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? - None at this time. ### How has the community developed since the last report? - 4 new JIRAs filed since the last report ### How has the project developed since the last report? - Working on 0.16.0-incubating release - Working on HBase 1.5 and 2.1 support ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [x] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: 2018-09-04 ### When were the last committers or PPMC members elected? - None since coming to incubation ### Have your mentors been helpful? - Mentors are helpful and responsive. - We do only have 2 mentors. ### Signed-off-by: - [X] (tephra) Alan Gates Comments: - [X] (tephra) James Taylor Comments: ### IPMC/Shepherd notes:
## Description:
- Apache Phoenix enables SQL-based OLTP and operational analytics for Apache
Hadoop
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Continuing an excellent stream of new committers and PMC members (details
below). Two more committers have been confirmed via a VOTE but are pending
acceptance and clerical tasks to complete the addition.
- 4.14.2 is nearing completion. RC0 was voted on, but did not pass.
- 5.0.1 is getting close to an initial vote, but has some
stabilization/cleanup work yet to do. Appears to be naturally queueing up
after 4.14.2 nicely.
- A community event ("NoSQL Day"), focusing on Accumulo, HBase, and Phoenix
is scheduled for May 21st in Washington, D.C. We have half a dozen Phoenix
specific talks accepted on the agenda for the event.
## Health report:
- Nothing notable to report. Trends are continuing per normal. Influx of
"new blood" is a boon to the community, reflected in a good number of
commits and reviews by "old" community members.
## PMC changes:
- Currently 30 PMC members.
- New PMC members:
- Chenglei (2019/04/09)
- Geoffrey Jacoby (2019/04/09)
## Committer base changes:
- Currently 42 committers.
- New committers:
- Mihir Monani (2019/04/27)
- Abhishek Singh Chouhan (2019/04/05)
## Releases:
- 4.14.1 was released on 2018/11/14
- 5.0.0 was released on 2018/07/14
## Mailing list activity:
- Activity is largely in-line with history. No significant changes to trends
to be identified.
Omid is a flexible, reliable, high performant and scalable ACID transactional framework that allows client applications to execute transactions on top of MVCC key/value-based NoSQL datastores (currently Apache HBase) providing Snapshot Isolation guarantees on the accessed data. Omid has been incubating since 2016-03-28. Three most important issues to address in the move towards graduation: 1. Optimise Omid for the integration with Apache Phoenix. 2. Document additional features added for the integration with Apache Phoenix, as well as, the low latency algorithm. 3. Get positive feedback from other projects currently in Apache. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? How has the community developed since the last report? Integration with Apache Phoenix was over, we are currently working on optimisation. How has the project developed since the last report? 1. Release 1.0.0 was published and includes all the Phoenix required features. 2. The Apache Phoenix code that uses Omid was committed and currently Omid serves as Phoenix transaction processor. 3. We are currently working on a minor release in Omid, 1.0.1, that includes optimization to Omid that inferred from the integration with Phoenix. These features mostly improve the performance of Omid, however, some are bug fixes that revealed by the integration with Phoenix while pushing Omid to its corner cases. We will start the release process in a few days. Jiras 124 - 135 will be part of the release. How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [ ] Community building [X] Nearing graduation [ ] Other: Date of last release: 2018-12-24 When were the last committers or PPMC members elected? 2018-09-25 Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Our mentors are extremely responsive and helpful. Signed-off-by: [X](omid) Alan Gates Comments: I don't see any of the issues listed under "Three most important issues to address in the move towards graduation" as blockers for graduation. The community has done multiple releases and added one committer. Development is slow but consistent. I do not believe the community has done a name search yet to make sure Omid is acceptable. AFAIK that is the only blocker for graduation. I've given this feedback to the community. [X](omid) James Taylor Comments: IPMC/Shepherd notes:
Tephra is a system for providing globally consistent transactions on top of Apache HBase and other storage engines. Tephra has been incubating since 2016-03-07. Two most important issues to address in the move towards graduation: 1. Improve community engagement 2. Increase adoption Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? - None at this time. How has the community developed since the last report? - 1 new JIRA filed since the last report - 1 new bug created since the last report How has the project developed since the last report? - Working on 0.16.0-incubating release How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [x] Community building [ ] Nearing graduation [ ] Other: Date of last release: 2018-09-04 When were the last committers or PPMC members elected? - None since coming to incubation Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. - Mentors are helpful and responsive Signed-off-by: [X](tephra) Alan Gates Comments: [X](tephra) James Taylor Comments: IPMC/Shepherd notes:
## Description:
- Apache Phoenix enables SQL-based OLTP and operational analytics for Apache
Hadoop
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- 4.14.1 was officially released. This release was in the final steps of
release at the time of that last board report (Nov 2018).
- We've added a new PMC member and new committers! Karan was added as a PMC
member. Four new committers joined our ranks: Akshita, Chinmay, Jaanai,
and Gerald.
- Regular development continues on the 4.x release line. The 5.x would
benefit from a new release in the near future.
## Health report:
- Activity remains constant on average. We had an expected tail-off during
the Christmas and (calendar) New Year with our predominantly US-based
membership.
## PMC changes:
- Currently 28 PMC members.
- New PMC members:
- Karan Mehta (2018/12/23)
## Committer base changes:
- Currently 40 committers.
- New committers:
- Akshita Malhotra (2019/01/21)
- Chinmay Kulkarni (2018/12/10)
- Jaanai Zhang (2019/01/02)
- Gerald Sangudi (2018/12/16)
## Releases:
- 4.14.1 was released on 2018/11/14
- 5.0.0 was released on 2018/07/14
## Mailing list activity:
- Activity is largely in-line with history. No significant changes to trends
to be identified.
Omid is a flexible, reliable, high performant and scalable ACID transactional framework that allows client applications to execute transactions on top of MVCC key/value-based NoSQL datastores (currently Apache HBase) providing Snapshot Isolation guarantees on the accessed data. Omid has been incubating since 2016-03-28. Three most important issues to address in the move towards graduation: 1. Finish integration with Apache Phoenix – Omid side was implemented and released. 2. Document additional features added for the integration with Apache Phoenix, as well as, the low latency algorithm. 3. Get positive feedback from other projects currently in Apache. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? N/A How has the community developed since the last report? New committer, Yonatan Gottesman, was added to Omid’s community. Yonatan is very active and contributed to the integration with Phoenix. Moreover, Yonattan implemented the low latency version of Omid which is currently part of release 1.0.0. Integration with Apache Phoenix will be ready in a few days, early December. How has the project developed since the last report? The vote for major release 1.0.0 passed successfully in the incubator general list. This release includes all the Phoenix required features. The release is currently being deployed to Nexus and a formal announcement of the release will be send shortly. Omid and Apache Phoenix integration is at its final stage. Omid release 1.0.0 includes all Phoenix required features, therefore, from the Omid side, the integration with Phoenix is over. The Phoenix code is also ready and currently located in a feature branch that will be merged in a few days. How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [ ] Community building [X] Nearing graduation [ ] Other: Date of last release: 2018-06-10 When were the last committers or PPMC members elected? 2018-09-25 Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. Our mentors are very helpful and responsive. We appreciate their help. Signed-off-by: [X](omid) Alan Gates Comments: [x](omid) James Taylor Comments: IPMC/Shepherd notes: Drew Farris (Shepherd) - Mentors active on the mailing lists, active development, and progress towards graduation observed.
Tephra is a system for providing globally consistent transactions on top of Apache HBase and other storage engines. Tephra has been incubating since 2016-03-07. Two most important issues to address in the move towards graduation: 1. Improve community engagement 2. Increase adoption Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? - None at this time. How has the community developed since the last report? - 1 new subscriber in dev mailing list since the last report How has the project developed since the last report? - Working on 0.16.0-incubating release How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [x] Community building [ ] Nearing graduation [ ] Other: Date of last release: 2018-09-04 When were the last committers or PPMC members elected? - None since coming to incubation Have your mentors been helpful and responsive or are things falling through the cracks? In the latter case, please list any open issues that need to be addressed. - Mentors are helpful and responsive Signed-off-by: [X](tephra) Alan Gates Comments: [X](tephra) James Taylor Comments: IPMC/Shepherd notes:
## Description:
- Apache Phoenix enables SQL-based OLTP and operational analytics for Apache
Hadoop
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- One release since last report: 4.14.1. The release was approved by the PMC
and is in the process of being released today (2018/11/14)
- Lars H. (PMC) organized a Phoenix Meetup for 2018/11/14 in San Francisco,
CA to be a general community-driven discussion. Notes will be taken and
posted to the dev-list for those unable to join physically and remotely.
- We've not added any new committers or PMC, but do have on-going discussions
as to who we want to invite for each. These threads need to be bump'ed.
## Health report:
- Activity remains relatively flat. Contributions and user-interactions
remain relatively consistent.
## PMC changes:
- Currently 27 PMC members.
- New PMC members:
- Pedro Boado was added to the PMC on Thu Jun 07 2018
- Vincent Poon was added to the PMC on Thu Jun 07 2018
## Committer base changes:
- Currently 36 committers.
- Ohad Shaham was added as a committer on Fri Jun 08 2018
## Releases:
- 4.14.1 was released on 2018/11/14
- 5.0.0 was released on Sat Jul 14 2018
## Mailing list activity:
- Activity is largely in-line with history. No significant changes to trends
to be identified.
Omid is a flexible, reliable, high performant and scalable ACID transactional framework that allows client applications to execute transactions on top of MVCC key/value-based NoSQL datastores (currently Apache HBase) providing Snapshot Isolation guarantees on the accessed data. Omid has been incubating since 2016-03-28. Three most important issues to address in the move towards graduation: 1. Get new committers. 2. Finish integration with Apache Phoenix. 3. Get positive feedback from other projects currently in Apache. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? N/A How has the community developed since the last report? 1. Integration with Apache Phoenix is at its final stage. 2. New active contributor, Yonatan Gottesman. How has the project developed since the last report? 1. Release 0.9.0 was released on June 10. 2. Omid low latency [OMID-90] committed to a feature branch. 3. Omid and Apache Phoenix integration is at its final stage. The Omid version for the integration is located at feature branch phoenix-integration. This feature branch will be the next release candidate that will start a release process in a few weeks. How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [X] Community building [ ] Nearing graduation [ ] Other: Date of last release: 2018-06-10 When were the last committers or PPMC members elected? Signed-off-by: [X](omid) Alan Gates Comments: A criterion for graduation is adding at least one committer to the project. So I believe "Community building" would be a more accurate assessment of your podling's maturity. [ ](omid) Lars Hofhansl Comments: [ ](omid) Flavio P. Junqueira Comments: [ ](omid) Thejas Nair Comments: [x](omid) James Taylor Comments: I've updated the community assessment to "Community building" based on Alan's feedback. Once a new committer is added to the project (which will happen soon), then we can update to "Nearing graduation". IPMC/Shepherd notes:
Tephra is a system for providing globally consistent transactions on top of Apache HBase and other storage engines. Tephra has been incubating since 2016-03-07. Two most important issues to address in the move towards graduation: 1. Improve community engagement 2. Increase adoption Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? - None at this time. How has the community developed since the last report? - 5 new JIRAs filed since the last report - 1 new subscriber in dev mailing list since the last report How has the project developed since the last report? - Tephra 0.15.0-incubating released How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [x] Community building [ ] Nearing graduation [ ] Other: Date of last release: 2018-09-04 When were the last committers or PPMC members elected? - None since coming to incubation Signed-off-by: [X](tephra) Alan Gates Comments: [ ](tephra) Andrew Purtell Comments: [x](tephra) James Taylor Comments: [ ](tephra) Lars Hofhansl Comments: IPMC/Shepherd notes: Dave Fisher: This podling thinks they are near graduation, but has never added any new committers/PPMC members. Not so sure. I sent a message to the podling about this. Alan Gates: This is my fault. See email thread https://lists.apache.org/thread.html413e06bde2263f2f56797e871b256ec1584f8c5 41fdc5e96857b13f5@%3Cdev.tephra.apache.org%3E where I started pushing them towards determining their future direction. I assumed they had added additional PPMC members without checking. I can take this feedback back to them and help them work through this. James Taylor: I've updated the community assessment to "Community building" based on the above feedback.
## Description:
- Apache Phoenix enables SQL-based OLTP and operational analytics for Apache
Hadoop
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Two major release: 4.14.0 and 5.0.0. The former targeted HBase-0.98 and
1.x major release lines, the latter targeted HBase-2.0.
- Post 4.14, we've decided to stop releases versions of Phoenix that support
HBase 0.98 and 1.1 releases as the HBase project has made a similar
decision on creating more releases of those versions.
- Created a new mailing list, issues@phoenix, to reduce overall traffic to
dev@phoenix.
- Held PhoenixCon on June 18th in San Jose, California, USA concurrently
with HBaseCon (same day, same space). We had roughly 150 people in
attendance at the events, with 10 Phoenix-specific talks given. Feedback
was overall positive. Recordings are available at
https://phoenix.apache.org/phoenixcon-archives.html for those who were
unable to physically attend the event.
- We've added two new PMC members and one new committer since our last
report.
## Health report:
- Things largely remain the same for the project. As HBase continues to
evolve into newer versions, it requires us to do the same in Phoenix. We
have continued activity in the project and I believe things look OK for
the future.
- Continuing to support and grow new contributors is a challenge.
## PMC changes:
- Currently 27 PMC members.
- New PMC members:
- Pedro Boado was added to the PMC on Thu Jun 07 2018
- Vincent Poon was added to the PMC on Thu Jun 07 2018
## Committer base changes:
- Currently 36 committers.
- Ohad Shaham was added as a committer on Fri Jun 08 2018
## Releases:
- 4.14.0 was released on Fri Jun 08 2018
- 5.0.0 was released on Sat Jul 14 2018
## Mailing list activity:
- List activity is largely consistent with previous months. There is a
slight down-tick in volume to users@phoenix.
Omid is a flexible, reliable, high performant and scalable ACID transactional framework that allows client applications to execute transactions on top of MVCC key/value-based NoSQL datastores (currently Apache HBase) providing Snapshot Isolation guarantees on the accessed data. Omid has been incubating since 2016-03-28. Three most important issues to address in the move towards graduation: 1. Boost project dissemination in the Apache community. 2. Collaborate/integrate Omid with other Apache projects. 3. Get positive feedback from other projects currently in Apache. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? N/A How has the community developed since the last report? Omid 0.9.0 released. Continue integration with Apache Phoenix. Pinterest exploring to use Omid in production. How has the project developed since the last report? Preparing 0.9.0 version. Solved issues related to legal stuff. Quarter Stats (from: 2017-03-01 to: 2018-05-31): +---------------------------------------------+ | Metric | counts | +---------------------------------------------+ | # of msgs in dev list | 192 | | Active Contributors (incl mentors)| 8 | | Jira New Issues | 10 | | Resolved Issues | 10 | | Pull Requests merged | 12 | | Pull Requests proposed | 14 | +---------------------------------------------+ How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [X] Community building [ ] Nearing graduation [ ] Other: Date of last release: 2018-05-29 When were the last committers or PPMC members elected? Signed-off-by: [X](omid) Alan Gates Comments: [ ](omid) Lars Hofhansl Comments: [ ](omid) Flavio P. Junqueira Comments: [ ](omid) Thejas Nair Comments: [X](omid) James Taylor Comments: IPMC/Shepherd notes:
Tephra is a system for providing globally consistent transactions on top of
Apache HBase and other storage engines.
Tephra has been incubating since 2016-03-07.
Two most important issues to address in the move towards graduation:
1. Improve community engagement
2. Increase adoption
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
- None at this time.
How has the community developed since the last report?
- 7 new JIRAs filed since the last report
How has the project developed since the last report?
- Completed the 0.14.0-incubating release
- Working on 0.15.0-incubating release
- Added support for HBase 2.0 (new major version of HBase)
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[x] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2018-05-30
When were the last committers or PPMC members elected?
- None since coming to incubation
Signed-off-by:
[X](tephra) Alan Gates
Comments: Sent following email to dev list after reading this report:
It seems development on Tephra has slowed quite a bit lately, with only 7
JIRAs filed during the last 3 months. I know Tephra is used in other
projects, like Apache Phoenix. Is this slowdown temporary? Is development
slowing because Tephra is mature and only maintenance is now required? Is
it continuing to be picked up by new projects or only used in 1 or 2
places? I ask because it feels like it is near time for Tephra to graduate
(it's been incubating for over 2 years now) and what needs to be done to
graduate is somewhat determined by the answers to these questions.
[ ](tephra) Andrew Purtell
Comments:
[x](tephra) James Taylor
Comments:
[ ](tephra) Lars Hofhansl
Comments:
IPMC/Shepherd notes:
}}}
Table of Contents
AriaTosca
Crail
Daffodil
Dubbo
Gearpump
Gossip
Griffin
Hivemall
Myriad
Nemo
Omid
OpenWhisk
Pulsar
Quickstep
S2Graph
SAMOA
SINGA
SkyWalking
Superset
Taverna
Tephra
Omid is a flexible, reliable, high performant and scalable ACID transactional framework that allows client applications to execute transactions on top of MVCC key/value-based NoSQL datastores (currently Apache HBase) providing Snapshot Isolation guarantees on the accessed data. Omid has been incubating since 2016-03-28. Three most important issues to address in the move towards graduation: 1. Boost project dissemination in the Apache community. 2. Collaborate/integrate Omid with other Apache projects. 3. Get positive feedback from other projects currently in Apache. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? N/A How has the community developed since the last report? Omid 0.9.0 released. Continue integration with Apache Phoenix. Pinterest exploring to use Omid in production. How has the project developed since the last report? Preparing 0.9.0 version. Solved issues related to legal stuff. Quarter Stats (from: 2017-03-01 to: 2018-05-31): +---------------------------------------------+ | Metric | counts | +---------------------------------------------+ | # of msgs in dev list | 192 | | Active Contributors (incl mentors)| 8 | | Jira New Issues | 10 | | Resolved Issues | 10 | | Pull Requests merged | 12 | | Pull Requests proposed | 14 | +---------------------------------------------+ How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [X] Community building [ ] Nearing graduation [ ] Other: Date of last release: 2018-05-29 When were the last committers or PPMC members elected? Signed-off-by: [X](omid) Alan Gates Comments: [ ](omid) Lars Hofhansl Comments: [ ](omid) Flavio P. Junqueira Comments: [ ](omid) Thejas Nair Comments: [X](omid) James Taylor Comments: IPMC/Shepherd notes:
Tephra is a system for providing globally consistent transactions on top of Apache HBase and other storage engines. Tephra has been incubating since 2016-03-07. Two most important issues to address in the move towards graduation: 1. Improve community engagement 2. Increase adoption Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? - None at this time. How has the community developed since the last report? - 7 new JIRAs filed since the last report How has the project developed since the last report? - Completed the 0.14.0-incubating release - Working on 0.15.0-incubating release - Added support for HBase 2.0 (new major version of HBase) How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [x] Community building [ ] Nearing graduation [ ] Other: Date of last release: 2018-05-30 When were the last committers or PPMC members elected? - None since coming to incubation Signed-off-by: [X](tephra) Alan Gates Comments: Sent following email to dev list after reading this report: It seems development on Tephra has slowed quite a bit lately, with only 7 JIRAs filed during the last 3 months. I know Tephra is used in other projects, like Apache Phoenix. Is this slowdown temporary? Is development slowing because Tephra is mature and only maintenance is now required? Is it continuing to be picked up by new projects or only used in 1 or 2 places? I ask because it feels like it is near time for Tephra to graduate (it's been incubating for over 2 years now) and what needs to be done to graduate is somewhat determined by the answers to these questions. [ ](tephra) Andrew Purtell Comments: [x](tephra) James Taylor Comments: [ ](tephra) Lars Hofhansl Comments: IPMC/Shepherd notes: }}}
## Description: - Apache Phoenix enables SQL-based OLTP and operational analytics for Apache Hadoop ## Issues: - There are no issues requiring board attention at this time ## Activity: - 4.14.0 release (rc0) being voted upon now - 5.0.0-alpha release completed mid-February - 5.0.0 release (rc0) incoming soon - Completed IP Clearance process to adopt a new codebase: a Python-based driver originally developed outside of Apache. - PhoenixCon is scheduled for June 18th in San Jose, California, USA. The event will be held concurrently with HBaseCon (same day, same space). A subset of PMC members are presently finalizing talks which will be given at the event. https://phoenix.apache.org/phoenixcon-2018/ ## Health report: - Overall the project is maintaining its healthy state. We have our strong core developers, a regular collection of users getting involved, new developers submitting fixes, and releases happening. PMC needs to evaluate contributors and committers for new committers and PMC members, respectively. ## PMC changes: - Currently 25 PMC members. - No new PMC members added in the last 3 months - Last PMC addition was Sergey Soldatov on Mon Oct 02 2017 ## Committer base changes: - Currently 35 committers. - No new committers added in the last 3 months - Last committer addition was Pedro Boado at Tue Jan 30 2018 ## Releases: - 5.0.0-alpha was released on Tue Feb 13 2018 ## Mailing list activity: - Both dev and user lists are trending upward slightly over the previous quarter but are not significantly different. ## JIRA activity: - 144 JIRA tickets created in the last 3 months - 135 JIRA tickets closed/resolved in the last 3 months
Omid is a flexible, reliable, high performant and scalable ACID transactional framework that allows client applications to execute transactions on top of MVCC key/value-based NoSQL datastores (currently Apache HBase) providing Snapshot Isolation guarantees on the accessed data. Omid has been incubating since 2016-03-28. Three most important issues to address in the move towards graduation: 1. Boost project dissemination in the Apache community. 2. Collaborate/integrate Omid with other Apache projects. 3. Get positive feedback from other projects currently in Apache. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? N/A How has the community developed since the last report? Apache Phoenix How has the project developed since the last report? HBase 0.x version being tested in prod environment at Yahoo. Preparing 0.9.0 version. Quarter Stats (from: 2017-12-01 to: 2018-02-28): +---------------------------------------------+ | Metric | counts | +---------------------------------------------+ | # of msgs in dev list | 108 | | Active Contributors (incl mentors)| 8 | | Jira New Issues | 2 | | Resolved Issues | 8 | | Pull Requests merged | 9 | | Pull Requests proposed | 3 | +---------------------------------------------+ How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [X] Community building [ ] Nearing graduation [ ] Other: Date of last release: 2016-06-24 When were the last committers or PPMC members elected? Signed-off-by: [ ](omid) Alan Gates Comments: [ ](omid) Lars Hofhansl Comments: [ ](omid) Flavio P. Junqueira Comments: [ ](omid) Thejas Nair Comments: [x](omid) James Taylor Comments:
Tephra is a system for providing globally consistent transactions on top of
Apache HBase and other storage engines.
Tephra has been incubating since 2016-03-07.
Two most important issues to address in the move towards graduation:
1. Improve community engagement
2. Increase adoption
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
- None at this time.
How has the community developed since the last report?
- 15 new JIRAs filed since the last report
- 1 external contributors submitted patches since the last report
- 1 external contributor created tickets in JIRA since the last report
How has the project developed since the last report?
- Working on 0.14.0-incubating release
- Adding support for HBase 2.0 (new major version of HBase)
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[x] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2017-09-21
When were the last committers or PPMC members elected?
- None since coming to incubation
Signed-off-by:
[ ](tephra) Alan Gates
Comments:
[ ](tephra) Andrew Purtell
Comments:
[x](tephra) James Taylor
Comments:
[ ](tephra) Lars Hofhansl
Comments:
## Description:
- Apache Phoenix enables SQL-based OLTP and operational analytics
for Apache Hadoop
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Released 4.13.0 and 4.13.2-CDH (first release compatible with Cloudera's
Distribution of Hadoop) in the last three months
- Voting underway on HBase 2.0 compatible release
- Revived support for HBase 1.1 and HBase 1.2 after community members
stepped up as release managers (one of which has become a committer).
## Health report:
- The project is healthy and continues to grow as users look for easy
ways to gain insight over and manage their ever-increasing Hadoop
data through standard SQL and JDBC APIs.
## PMC changes:
- Currently 25 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Sergey Soldatov on Mon Oct 02 2017
## Committer base changes:
- Currently 35 committers.
- New commmitters:
- Karan Mehta was added as a committer on Wed Dec 20 2017
- Pedro Boado was added as a committer on Tue Jan 30 2018
## Releases:
- 4.13.0 was released on Thu Nov 09 2017
- 4.13.2-CDH was released on Sat Jan 20 2018
## Mailing list activity:
- Mailing list subscriptions are flat
- dev@phoenix.apache.org:
- 228 subscribers (up 5 in the last 3 months):
- 2661 emails sent to list (2996 in previous quarter)
- user@phoenix.apache.org:
- 551 subscribers (down -1 in the last 3 months):
- 236 emails sent to list (215 in previous quarter)
## JIRA activity:
- 224 JIRA tickets created in the last 3 months
- 147 JIRA tickets closed/resolved in the last 3 months
Omid is a flexible, reliable, high performant and scalable ACID transactional
framework that allows client applications to execute transactions on top of
MVCC key/value-based NoSQL datastores (currently Apache HBase) providing
Snapshot Isolation guarantees on the accessed data.
Omid has been incubating since 2016-03-28.
Three most important issues to address in the move towards graduation:
1. Boost project dissemination in the Apache community.
2. Collaborate/integrate Omid with other Apache projects.
3. Get positive feedback from other projects currently in Apache.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
N/A
How has the community developed since the last report?
Continue integration with Apache Phoenix
How has the project developed since the last report?
Critical fixes on security and HBase 0.x & 1.x integration.
HBase 0.x version being tested in prod environment at Yahoo.
Started testing HBase version 1.x in local environments.
Quarter Stats (from: 2017-09-01 to: 2017-11-30):
+---------------------------------------------+
| Metric | counts |
+---------------------------------------------+
| # of msgs in dev list | 53 |
| Active Contributors (incl mentors)| 8 |
| Jira New Issues | 5 |
| Resolved Issues | 1 |
| Pull Requests merged | 1 |
| Pull Requests proposed | 2 |
+---------------------------------------------+
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2016-06-24
When were the last committers or PPMC members elected?
Signed-off-by:
[X](omid) Alan Gates
Comments:
[ ](omid) Lars Hofhansl
Comments:
[ ](omid) Flavio P. Junqueira
Comments:
[ ](omid) Thejas Nair
Comments:
[x](omid) James Taylor
Comments:
Tephra is a system for providing globally consistent transactions on top of
Apache HBase and other storage engines.
Tephra has been incubating since 2016-03-07.
Two most important issues to address in the move towards graduation:
1. Improve community engagement
2. Increase adoption
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
- None at this time.
How has the community developed since the last report?
- 1 new subscriber in dev mailing list since the last report
- 18 new JIRAs filed since the last report
- 1 external contributors submitted patches since the last report
- 1 external contributor created a ticket in JIRA since the last report
How has the project developed since the last report?
- Tephra 0.13.0-incubating released
- Working on 0.14.0-incubating release
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[x] Community building
[ ] Nearing graduation
[ ] Other:
Date of the last release:
2017-09-21
When were the last committers or PMC members elected?
- None since coming to incubation
Signed-off-by:
[X](tephra) Alan Gates
Comments:
[ ](tephra) Andrew Purtell
Comments:
[x](tephra) James Taylor
Comments:
[ ](tephra) Lars Hofhansl
Comments:
## Description:
- Apache Phoenix enables SQL-based OLTP and operational analytics
for Apache Hadoop
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Released 4.12.0 and 4.13.0 in the last three months
- Ongoing work to support HBase 2.0 with good collaboration between
HBase and Phoenix communities
- Dropping support for HBase 1.1 and HBase 1.2 after discussion due
to lack of interest/need (no one volunteered to be RM).
- Continuing HBase 0.98 support for another couple releases, but
moving toward maintenance-only mode.
## Health report:
- The project is healthy and continues to grow as users look for easy
ways to gain insight over and manage their ever-increasing Hadoop
data through standard SQL and JDBC APIs.
## PMC changes:
- Currently 25 PMC members.
- Sergey Soldatov was added to the PMC on Mon Oct 02 2017
## Committer base changes:
- Currently 33 committers.
- New commmitters:
- Ethan Wang was added as a committer on Tue Oct 10 2017
- Vincent Poon was added as a committer on Thu Oct 12 2017
## Releases:
- 4.12.0 was released on Tue Oct 10 2017
- 4.13.0 was released on Thu Nov 09 2017
## Mailing list activity:
- Mailing list subscriptions remain relatively constant
- dev@phoenix.apache.org:
- 223 subscribers (down -3 in the last 3 months):
- 3350 emails sent to list (2950 in previous quarter)
- user@phoenix.apache.org:
- 553 subscribers (up 7 in the last 3 months):
- 245 emails sent to list (271 in previous quarter)
## JIRA activity:
- More JIRAs filed than closed due mostly to lack of grooming
of backlog.
- 281 JIRA tickets created in the last 3 months
- 185 JIRA tickets closed/resolved in the last 3 months
Omid is a flexible, reliable, high performant and scalable ACID transactional
framework that allows client applications to execute transactions on top of
MVCC key/value-based NoSQL datastores (currently Apache HBase) providing
Snapshot Isolation guarantees on the accessed data.
Omid has been incubating since 2016-03-28.
Three most important issues to address in the move towards graduation:
1. Boost project dissemination in the Apache community.
2. Collaborate/integrate Omid with other Apache projects.
3. Get positive feedback from other projects currently in Apache.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
N/A
How has the community developed since the last report?
Started integration with Apache Phoenix
How has the project developed since the last report?
Several bugs discovered and fixed.
Continue testing prod environment at Yahoo.
Branch 0.9.0.0 started for next release
Quarter Stats (from: 2017-03-01 to: 2017-05-31):
+---------------------------------------------+
| Metric | counts |
+---------------------------------------------+
| # of msgs in dev list | 108 |
| Active Contributors (incl mentors)| 8 |
| Jira New Issues | 6 |
| Resolved Issues | 6 |
| Pull Requests merged | 3 |
| Pull Requests proposed | 3 |
+---------------------------------------------+
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2016-06-24
When were the last committers or PPMC members elected?
Signed-off-by:
[X](omid) Alan Gates
Comments: Activity continues to be low but there has been a noticeable uptick since the last report, and there is now a consistent if low level of activity on the project. The big challenge now for Omid is to attract new contributors to the project.
[ ](omid) Lars Hofhansl
Comments:
[ ](omid) Flavio P. Junqueira
Comments:
[ ](omid) Thejas Nair
Comments:
[X](omid) James Taylor
Comments:
Tephra is a system for providing globally consistent transactions on top of
Apache HBase and other storage engines.
Tephra has been incubating since 2016-03-07.
Two most important issues to address in the move towards graduation:
1. Improve community engagement
2. Increase adoption
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
- None at this time.
How has the community developed since the last report?
- 1 new subscriber in dev mailing list since the last report
- 16 new JIRAs filed since the last report
- 2 external contributors submitted patches since the last report
- 4 external contributor created a ticket in JIRA since the last report
How has the project developed since the last report?
- Working on 0.13.0-incubating release
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[x] Community building
[ ] Nearing graduation
[ ] Other:
Date of the last release:
2017-05-30
When were the last committers or PMC members elected?
- None since coming to incubation
Signed-off-by:
[X](tephra) Alan Gates
Comments:
[ ](tephra) Andrew Purtell
Comments:
[X](tephra) James Taylor
Comments:
[ ](tephra) Lars Hofhansl
Comments:
## Description:
- Apache Phoenix enables SQL-based OLTP and operational analytics
for Hadoop using Apache HBase as its backing store.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- PhoenixCon 2017 was hosted by Salesforce on June 13th. Attendance was
good (~75 people) and we had some good community discussions.
- Phoenix 4.11 was released in late June and work.
- Work toward Phoenix 4.12 is well underway with lots of stabilization
around mutable secondary indexes and some solid contributions from
potential new committers in the area of table sampling and approximate
count.
## Health report:
- The project is healthy and continues to grow as users look for easy
ways to gain insight over and manage their ever-increasing Hadoop
data through standard SQL and JDBC APIs.
## PMC changes:
- Currently 24 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Josh Elser on Tue Aug 09 2016
## Committer base changes:
- Currently 31 committers.
- No new committers added in the last 3 months
- Last committer addition was Geoffrey Jacoby at Sun Feb 26 2017
## Releases:
- Last release was 4.11.0 on Tue Jun 20 2017
## Mailing list activity:
- Mailing list activity is steady.
- dev@phoenix.apache.org:
- 226 subscribers (down -1 in the last 3 months):
- 3048 emails sent to list (2033 in previous quarter)
- user@phoenix.apache.org:
- 546 subscribers (down -1 in the last 3 months):
- 280 emails sent to list (345 in previous quarter)
## JIRA activity:
- 233 JIRA tickets created in the last 3 months
- 160 JIRA tickets closed/resolved in the last 3 months
Omid is a flexible, reliable, high performant and scalable ACID transactional
framework that allows client applications to execute transactions on top of
MVCC key/value-based NoSQL datastores (currently Apache HBase) providing
Snapshot Isolation guarantees on the accessed data.
Omid has been incubating since 2016-03-28.
Three most important issues to address in the move towards graduation:
1. Boost project dissemination in the Apache community.
2. Collaborate/integrate Omid with other Apache projects.
3. Get positive feedback from other projects currently
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
N/A
How has the community developed since the last report?
2 new contributors
Omid presented in the Apache Conf US in comparison to other Apache TMs for
HBase. It will be presented also in HBase conf in mid June.
Meeting with Apache Tephra contributors
How has the project developed since the last report?
Several bugs discovered and working on fixes.
Continue working on next release. Testing in prod env.
Quarter Stats (from: 2017-03-01 to: 2017-05-31):
+---------------------------------------------+
| Metric | counts |
+---------------------------------------------+
| # of msgs in dev list | 60 |
| Active Contributors (incl mentors)| 8 |
| Jira New Issues | 8 |
| Resolved Issues | 2 |
| Pull Requests merged | 1 |
| Pull Requests proposed | 3 |
+---------------------------------------------+
How would you assess the podling's maturity? Please feel free to add your own
commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2016-06-24
When were the last committers or PPMC members elected?
Signed-off-by:
[X](omid) Alan Gates
Comments: In the past I have made comments on the lack of activity on
this podling. While activity is still low it has definitely picked up
with several JIRAs being filed and fixed and user queries appearing on
the mailing list and being answered. It's good to see this pickup in
activity.
[ ](omid) Lars Hofhansl
Comments:
[X](omid) Flavio P. Junqueira
Comments:
[ ](omid) Thejas Nair
Comments:
[X](omid) James Taylor
Comments:
Tephra is a system for providing globally consistent transactions on top of
Apache HBase and other storage engines.
Tephra has been incubating since 2016-03-07.
Two most important issues to address in the move towards graduation:
1. Improve community engagement 2. Increase adoption
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
- None at this time.
How has the community developed since the last report?
- Andreas Neumann talked about Apache Tephra as part of his talk on
"Transactions in Hadoop" at ApacheCon BigData North America 2017 in Miami,
Florida, USA
- 2 new subscribers in dev mailing list since the last report
- 4 new JIRAs filed since the last report
- 0 external contributors submitted patches since the last report
- 1 external contributor created a ticket in JIRA since the last report
How has the project developed since the last report?
- Working on 0.13.0-incubating release
- Released 0.12.0-incubating
How would you assess the podling's maturity? Please feel free to add your own
commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2016-05-23
When were the last committers or PPMC members elected?
None since coming to incubation
Signed-off-by:
[X](tephra) Alan Gates
Comments:
[ ](tephra) Andrew Purtell
Comments:
[X](tephra) James Taylor
Comments:
[ ](tephra) Lars Hofhansl
Comments:
## Description:
- Apache Phoenix enables SQL-based OLTP and operational analytics
for Hadoop using Apache HBase as its backing store.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Successfully released 4.10.0 with substantial performance
improvements for write-once/append only use cases.
- Planning for PhoenixCon 2017 is going well: 120 attendees have
RSVPed and we have 7 talks submitted. Event is scheduled for
Tue June 13th.
## Health report:
- The project is healthy and continues to grow as users look for easy
ways to gain insight over and manage their ever-increasing Hadoop
data through standard SQL and JDBC APIs.
## PMC changes:
- Currently 24 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Josh Elser on Tue Aug 09 2016
## Committer base changes:
- Currently 31 committers.
- New commmitters:
- Chenglei was added as a committer on Wed Feb 22 2017
- Geoffrey Jacoby was added as a committer on Sun Feb 26 2017
## Releases:
- 4.10.0 was released on Mon Mar 13 2017
## JIRA activity:
- 181 JIRA tickets created in the last 3 months
- 121 JIRA tickets closed/resolved in the last 3 months
Omid is a flexible, reliable, high performant and scalable ACID transactional
framework that allows client applications to execute transactions on top of
MVCC key/value-based NoSQL datastores (currently Apache HBase) providing
Snapshot Isolation guarantees on the accessed data.
Omid has been incubating since 2016-03-28.
Three most important issues to address in the move towards graduation:
1. Boost project dissemination in the Apache community.
2. Collaborate/integrate Omid with other Apache projects.
3. Get positive feedback from other projects currently
integrating/using Omid.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
N/A
How has the community developed since the last report?
Started integration with Apache Phoenix community.
Omid presented in the SF HBase community event in Dec.
Omid paper accepted in FAST 2017
How has the project developed since the last report?
Started working in the next release.
Quarter Stats (from: 2016-12-01 to: 2017-02-28):
+---------------------------------------------+
| Metric | counts |
+---------------------------------------------+
| # of msgs in dev list | 36 |
| Active Contributors (incl mentors)| 6 |
| Jira New Issues | 4 |
| Resolved Issues | 2 |
| Pull Requests merged | 0 |
| Pull Requests proposed | 0 |
+---------------------------------------------+
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2016-06-24
When were the last committers or PPMC members elected?
At incubation acceptance (2016-03-28)
Signed-off-by:
[X](omid) Alan Gates
Comments:
Activity on this podling remains low but it is good to see a few
issues files and resolved and the report filed on time and without
prodding by the mentors.
[ ](omid) Lars Hofhansl
Comments:
[ ](omid) Flavio P. Junqueira
Comments:
[ ](omid) Thejas Nair
Comments:
[ ](omid) James Taylor
Comments:
Tephra is a system for providing globally consistent transactions on top of Apache HBase and other storage engines. Tephra has been incubating since 2016-03-07. Three most important issues to address in the move towards graduation: 1. Regular releases 2. Improve community engagement 3. Increase adoption Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? - None at this time. How has the community developed since the last report? - 1 new subscriber in dev mailing list since the last report - 25 new JIRAs filed since the last report - 0 external contributors submitted patches since the last report - 1 external contributor created a ticket in JIRA since the last report How has the project developed since the last report? - Working on 0.11.0-incubating release - Released 0.10.0-incubating How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [x] Community building [ ] Nearing graduation [ ] Other: Date of the last release: 2016-12-16 When were the last committers or PMC members elected? - None since coming to incubation Signed-off-by: [X](tephra) Alan Gates Comments: [X](tephra) Andrew Purtell Comments: [ ](tephra) James Taylor Comments: [ ](tephra) Lars Hofhansl Comments:
## Description:
- Apache Phoenix enables SQL-based OLTP and operational analytics
for Apache Hadoop using Apache HBase as its backing store.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Plan to release 4.10.0 in Feb with some substantial performance
improvements.
- Work progressing on a 5.0 release leveraging Apache Calcite.
## Health report:
- The project is healthy and continues to grow as users look for easy
ways to gain insight over and manage their ever-increasing Hadoop
data through standard SQL and JDBC APIs.
## PMC changes:
- Currently 24 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Josh Elser on Tue Aug 09 2016
## Committer base changes:
- Currently 29 committers.
- Kevin Liew was added as a committer on Thu Nov 10 2016
## Releases:
- 4.9.0 was released on Tue Nov 22 2016
## Mailing list activity:
- Both dev and user lists continue to gain subscribers
- dev@phoenix.apache.org:
- 223 subscribers (up 4 in the last 3 months):
- 2328 emails sent to list (3652 in previous quarter)
- user@phoenix.apache.org:
- 550 subscribers (up 29 in the last 3 months):
- 270 emails sent to list (622 in previous quarter)
## JIRA activity:
- 215 JIRA tickets created in the last 3 months
- 121 JIRA tickets closed/resolved in the last 3 months
Omid is a flexible, reliable, high performant and scalable ACID transactional framework that allows client applications to execute transactions on top of MVCC key/value-based NoSQL datastores (currently Apache HBase) providing Snapshot Isolation guarantees on the accessed data. Omid has been incubating since 2016-03-28. Three most important issues to address in the move towards graduation: 1. Boost project dissemination in the Apache community. 2. Collaborate/integrate Omid with other Apache projects. 3. Get positive feedback from other projects currently integrating/using Omid. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? N/A How has the community developed since the last report? Initiated contact with Apache Phoenix community to integrate Omid. Blog entries published in Yahoo Engineering and Hadoop blogs. Article about Apache Omid incubation published in Datanami. Talk proposal on Omid sent to DataWorks Summit EU 2017 Quarter Stats (from: 2016-09-01 to: 2016-11-30): +---------------------------------------------+ | Metric | counts | +---------------------------------------------+ | # of msgs in dev list | 20 | | Active Contributors (incl mentors)| 6 | | Jira New Issues | 2 | | Resolved Issues | 1 | | Pull Requests merged | 0 | | Pull Requests proposed | 0 | +---------------------------------------------+ How has the project developed since the last report? In the process of completing its second release under in the Apache incubator. Date of last release: 2016-06-24 When were the last committers or PMC members elected? At incubation acceptance (2016-03-28) Signed-off-by: [ ](omid) Alan Gates [ ](omid) Lars Hofhansl [x](omid) Flavio P. Junqueira [ ](omid) Thejas Nair [ ](omid) James Taylor Shepherd/Mentor notes: Alan Gates: I'm concerned about this podling. The last commit was on August 15. Discounting broadcast and reminders, there have been no emails on the dev list since October, and there were only 3 that month. I've sent email on the dev list asking if people are still actively involved. Flavio Junqueira: I second Alan's concern, there has been very little activity in the last period for this podling.
Tephra is a system for providing globally consistent transactions on top of Apache HBase and other storage engines. Tephra has been incubating since 2016-03-07. Three most important issues to address in the move towards graduation: 1. Regular releases 2. Improve community engagement 3. Increase adoption Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? - None at this time. How has the community developed since the last report? - 18 subscribers in dev mailing list - 21 new JIRAs filed since the last report - 4 external contributors submitted patches since the last report How has the project developed since the last report? - Working on 0.10.0 release - Released 0.9.0 Date of the last release: 2016-09-18 When were the last committers or PMC members elected? - None since coming to incubation Signed-off-by: [X](tephra) Alan Gates [ ](tephra) Andrew Purtell [x](tephra) James Taylor [ ](tephra) Lars Hofhansl Shepherd/Mentor notes: Drew Farris (Shepherd): Two mentors active on mailing lists. Project is building towards a healthy community.
## Description:
- Apache Phoenix enables SQL-based OLTP and operational analytics
for Apache Hadoop
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Released 4.8 and 4.8.1 in the last three months
- Voting underway on a 4.9 and 4.8.2 release
- New committer (kliew) has been added
- Work progressing on a 5.0 release leveraging Apache Calcite.
## Health report:
- The project is healthy and continues to grow as users look for easy
ways to gain insight over and manage their ever-increasing Hadoop
data through standard SQL and JDBC APIs.
## PMC changes:
- Currently 24 PMC members.
- Josh Elser was added to the PMC on Tue Aug 09 2016
## Committer base changes:
- Currently 29 committers.
- Kevin Liew was added as a committer on Thu Nov 10 2016
## Releases:
- 4.8.0 was released on Tue Aug 09 2016
- 4.8.1 was released on Mon Sep 26 2016
## Mailing list activity:
- Both dev and user lists continue to gain subscribers
- dev@phoenix.apache.org:
- 219 subscribers (up 7 in the last 3 months):
- 3876 emails sent to list (3688 in previous quarter)
- user@phoenix.apache.org:
- 521 subscribers (up 12 in the last 3 months):
- 615 emails sent to list (389 in previous quarter)
## JIRA activity:
- 299 JIRA tickets created in the last 3 months
- 193 JIRA tickets closed/resolved in the last 3 months
Omid is a flexible, reliable, high performant and scalable ACID transactional framework that allows client applications to execute transactions on top of MVCC key/value-based NoSQL datastores (currently Apache HBase) providing Snapshot Isolation guarantees on the accessed data. Omid has been incubating since 2016-03-28. Three most important issues to address in the move towards graduation: 1. Boost project dissemination in the Apache community. 2. Collaborate/integrate Omid with other Apache projects. 3. Get positive feedback from other projects currently integrating/using Omid. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? N/A How has the community developed since the last report? * Omid presented at Hadoop Summit 2016 in San Jose. Some attendants manifested interest and asked for future plans of integrating Omid with Apache Phoenix. * First contact with Apache DistributedLog community for a possible integration with Omid. * Blog entry on Apache Omid ready to be published in Yahoo's hadoop blog site. * Quarter Stats (from: 2016-06-01 to: 2016-08-31): +---------------------------------------------+ | Metric | counts | +---------------------------------------------+ | # of msgs in dev list | 204 | | Active Contributors (incl mentors)| 6 | | Jira New Issues | 10 | | Resolved Issues | 12 | | Pull Requests merged | 7 | | Pull Requests proposed | 10 | +---------------------------------------------+ How has the project developed since the last report? First version of Omid released under the Apache incubator program. It has also been integrated with the Apache Hive project.F Date of last release: 2016-06-24 When were the last committers or PMC members elected? At incubation acceptance (2016-03-28) Signed-off-by: [X](omid) Alan Gates [ ](omid) Lars Hofhansl [x](omid) Flavio P. Junqueira [ ](omid) Thejas Nair [x](omid) James Taylor
Tephra is a system for providing globally consistent transactions on top of Apache HBase and other storage engines. Tephra has been incubating since 2016-03-07. Three most important issues to address in the move towards graduation: 1. Regular releases 2. Improve community engagement 3. Increase adoption Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? - None at this time. How has the community developed since the last report? - 12 subscribers in dev mailing list - 5 new JIRAs filed since last report - 2 new contributors submitted patches How has the project developed since the last report? - Working on 0.9.0 release Date of last release: 2016-05-31 When were the last committers or PMC members elected? - None since coming to incubation Signed-off-by: [X](tephra) Alan Gates [X](tephra) Andrew Purtell [X](tephra) Henry Saputra [x](tephra) James Taylor [ ](tephra) Lars Hofhansl
## Description:
- Apache Phoenix enables SQL-based OLTP and operational analytics
for Apache Hadoop
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- The first inaugural PhoenixCon, a dual track Meetup, was hosted by
Salesforce.com on Wed May 25th with attendance of ~100 people.
- Three Phoenix talks were given at Hadoop Summit on June 28-30.
- One Phoenix talk was given at HBaseCon on Tue May 24.
- Support for Phoenix 4.7 was added to Amazon EMR on Thu June 2.
- Cloudera Labs version of Phoenix was updated to 4.7 on Mon June 27.
## Health report:
- The project is healthy and continues to grow as users look for easy ways to
gain insight over and manage their ever-increasing Hadoop data through
standard SQL and JDBC APIs.
## PMC changes:
- Currently 24 PMC members.
- Josh Elser was added to the PMC on Wed August 10 2016
## Committer base changes:
- Currently 28 committers.
- Sergey Soldatov was added as a committer on Wed May 18 2016
## Releases:
- Phoenix 4.8.0 was released on Wed August 10 2016
## Mailing list activity:
- Both dev and user lists continue to gain subscribers
- dev@phoenix.apache.org:
- 211 subscribers (up 11 in the last 3 months):
- 3807 emails sent to list (3124 in previous quarter)
- user@phoenix.apache.org:
- 509 subscribers (up 32 in the last 3 months):
- 398 emails sent to list (729 in previous quarter)
## JIRA activity:
- 275 JIRA tickets created in the last 3 months
- 190 JIRA tickets closed/resolved in the last 3 months
Tephra is a system for providing globally consistent transactions on top of Apache HBase and other storage engines. Tephra has been incubating since 2016-03-07. Three most important issues to address in the move towards graduation. 1. Regular releases 2. Improve community engagement 3. Increase adoption Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? - None at this time. How has the community developed since the last report? 1. Started to see mailing list and JIRA activity from non-PMC members. How has the project developed since the last report? 1. tephra.incubator.apache.org website setup is complete. 2. Apache Tephra JIRA setup is complete. Date of last release: 2016-05-31 When were the last committers or PMC members elected? - None since coming to incubation Signed-off-by: [X](tephra) Alan Gates [ ](tephra) Andrew Purtell [X](tephra) Henry Saputra [ ](tephra) James Taylor [ ](tephra) Lars Hofhansl
Omid is a flexible, reliable, high performant and scalable ACID transactional framework that allows client applications to execute transactions on top of MVCC key/value-based NoSQL datastores (currently Apache HBase) providing Snapshot Isolation guarantees on the accessed data. Omid has been incubating since 2016-03-28. Three most important issues to address in the move towards graduation: 1. Code and documentation successfully moved into the Apache infrastructure (See https://git-wip-us.apache.org/repos/asf?p=incubator-omid.git & http://omid.incubator.apache.org/) 2. Prepared release guide (https://cwiki.apache.org/confluence/display/OMID/Omid+Release+process), first release (0.8.2) under Apache (https://cwiki.apache.org/confluence/display/OMID/Omid+Release+0.8.2.0) and upload binaries to Maven Central 3. Active collaboration started with another Apache community: Apache Hive Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? N/A How has the community developed since the last report? * Talk submitted to Hadoop Summit. It was accepted and will be presented on 2016-06-29 * The Hive community is using Omid to integrate with HBase for their metastore requirements * First contact with the Apache Phoenix community for a possible integration of Omid as a transaction manager for the SQL layer Phoenix provides * Quarter Stats (from: 2016-05-17 -project moved into Apache- to: 2016-06-03): +---------------------------------------------+ | Metric | counts | +---------------------------------------------+ | # of msgs in dev list | 303 | | Active Contributors (incl mentors)| 6 | | Jira New Issues | 27 | | Resolved Issues | 31 | | Pull Requests merged | 9 | | Pull Requests proposed | 12 | +---------------------------------------------+ How has the project developed since the last report? N/A, this is the first report since joining the Apache Incubation program Date of last release: 2016-06-06 When were the last committers or PMC members elected? At incubation acceptance (2016-03-28) Signed-off-by: [x](omid) Daniel Dai (Champion) [X](omid) Alan Gates [ ](omid) Lars Hofhansl [X](omid) Flavio P. Junqueira [ ](omid) Thejas Nair [ ](omid) James Taylor
Tephra is a system for providing globally consistent transactions on top of Apache HBase and other storage engines. Tephra has been incubating since 2016-03-07. Three most important issues to address in the move towards graduation: 1. Complete project setup 2. Regular releases 3. Improve community engagement Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? There are no issues requiring board attention at this time How has the community developed since the last report? 1) Apache Tephra now powers ACID transactions in Apache Phoenix (since v4.7.0). 2) We presented Apache Tephra as a part of the Apache Phoenix talk at HBaseCon 2016. 3) We also presented a more elaborate version of the above talk at PhoenixCon 2016. 4) We are making progress towards setting up of Project page. How has the project developed since the last report? 1) We had our first release (0.8.0-incubating) since incubation. 2) We have added support for Apache HBase v1.2 in the latest release (0.8.0-incubating). Date of last release: 2016-05-31 When were the last committers or PMC members elected? None since the May 2016 report Signed-off-by: [X](tephra) Alan Gates [X](tephra) Andrew Purtell [ ](tephra) Henry Saputra [X](tephra) James Taylor [ ](tephra) Lars Hofhansl
## Description: Apache Phoenix enables OLTP and SQL-based operational analytics for Apache Hadoop. ## Issues: There are no issues requiring board attention at this time ## Activity: - ACID transaction support was released in 4.7.0 as beta. - Four GSoC students have been paired with PMC members to pursue various Phoenix projects. - Good progress toward a 4.8.0 release with development expected to ramp down over the next few weeks. - Work continues to retrofit Phoenix to run on top of Apache Calcite to gain complete ANSI SQL support and improve interop with other Hadoop projects. ## Health report: The project is healthy and continues to grow as users look for easy ways to gain insight over and manage their ever-increasing Hadoop data through standard SQL and JDBC APIs. ## PMC changes: - Currently 23 PMC members. - Ankit Singhal was added to the PMC on Sun May 01 2016 ## Committer base changes: - Currently 27 committers. - Josh Elser was added as a committer on Fri Apr 08 2016 ## Releases: - Phoenix 4.7.0 was released on Tue Mar 08 2016 ## Mailing list activity: - Both dev and user lists continue to gain subscribers - dev@phoenix.apache.org: - 199 subscribers (up 13 in the last 3 months): - 3197 emails sent to list (4167 in previous quarter) - user@phoenix.apache.org: - 477 subscribers (up 30 in the last 3 months): - 740 emails sent to list (551 in previous quarter) ## JIRA activity: - 219 JIRA tickets created in the last 3 months - 137 JIRA tickets closed/resolved in the last 3 months
Tephra is a system for providing globally consistent transactions on top of Apache HBase and other storage engines. Tephra has been incubating since 2016-03-07. Three most important issues to address in the move towards graduation: 1. Complete project setup 2. Regular releases 3. Improve community engagement Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? - None at this time. How has the community developed since the last report? - Mailing lists have been created. - Working on the project page. How has the project developed since the last report? - Project is in initial setup phase. - SGA has been submitted, and git repo is set up. - Waiting for other bootstrapping tasks like JIRA import to be done. - Working towards the first release. Date of last release: None When were the last committers or PMC members elected? - None since coming to incubation Signed-off-by: [ ](tephra) Alan Gates [X](tephra) Andrew Purtell [ ](tephra) Henry Saputra [x](tephra) James Taylor [ ](tephra) Lars Hofhansl
## Description:
- Apache Phoenix is a relational database layer on top of Apache HBase
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- James Taylor presented Phoenix at Big Data Application Meetup on 1/27/16
- Vote underway on 4.7.0 release with next RC scheduled for next week.
- Transaction support added through integration with Tephra, an ASL 2.0
licensed project from Cask.
- Work continues to integrate Phoenix with Apache Calcite.
- Pull request is available to add Apache Sqoop support for Phoenix
## Health report:
- Health is good with the community continuing to grow and multiple
integration efforts underway to expand usage of Phoenix in the broader
Hadoop ecosystem.
## PMC changes:
- Currently 22 PMC members.
- Thomas D'Silva was added to the PMC on Fri Nov 20 2015
## Committer base changes:
- Currently 26 committers.
- Ankit Singhal was added as a committer on Mon Feb 01 2016
## Releases:
- Last release was 4.6.0 on Fri Oct 23 2015
## Mailing list activity:
- dev@phoenix.apache.org:
- 186 subscribers (up 8 in the last 3 months):
- 4374 emails sent to list (2241 in previous quarter)
- user@phoenix.apache.org:
- 446 subscribers (up 33 in the last 3 months):
- 592 emails sent to list (719 in previous quarter)
## JIRA activity:
- 269 JIRA tickets created in the last 3 months
- 361 JIRA tickets closed/resolved in the last 3 months
## Description:
Apache Phoenix is a relational database layer on top of Apache HBase.
## Issues:
There are no issues requiring board attention at this time
## Activity:
- Nick Dimiduk gave a talk on Phoenix at Apache Big Data 2015, Budapest.
- Capital One hosted a Phoenix Meetup in San Francisco on Wed Sep 16 2015.
- Hortonworks offerred a free SQL on Hadoop Masterclass in Paris featuring
Phoenix on Fri Nov 06 2015.
- Transaction support through integration with Tephra, an ASL 2.0 licensed
library is nearly complete.
- Work continues to integrate Phoenix with Apache Calcite.
- A new initiative, Drillix has begun to enable Phoenix to be used with
Apache Drill.
- A pull request is available to add Apache Sqoop support for Phoenix.
## Health report:
Health is good with the community continuing to grow and multiple
integration efforts underway to expand usage of Phoenix in the broader
Hadoop ecosystem.
## PMC changes:
- Currently 21 PMC members.
- New PMC members:
- Josh Mahonin was added to the PMC on Sun Nov 08 2015
## Committer base changes:
- Currently 25 committers.
- New commmitters:
- Jan Fernando was added as a committer on Wed Sep 30 2015
- Dumindu Buddhika was added as a committer on Thu Sep 17 2015
## Releases:
- 4.5.1 was released on Wed Aug 19 2015
- 4.6.0 was released on Fri Oct 23 2015
## Mailing list activity:
- dev@phoenix.apache.org:
- 179 subscribers (up 11 in the last 3 months):
- 2398 emails sent to list (2679 in previous quarter)
- user@phoenix.apache.org:
- 411 subscribers (up 48 in the last 3 months):
- 732 emails sent to list (654 in previous quarter)
## JIRA activity:
- 218 JIRA tickets created in the last 3 months
- 133 JIRA tickets closed/resolved in the last 3 months
## Description:
Apache Phoenix is a relational database layer on top of Apache HBase.
## Activity:
- Two minor versions released across our three supported HBase versions
- Highlights of the releases are outlined here: http://s.apache.org/7jk
- Several new modules were added:
* Query server
* Spark integration
* Pherf test at scale tool
- Phoenix was included in Cloudera Labs on May 6, 2015
- James Taylor gave a talk on Phoenix at Hadoop Summit on June 10, 2015
## Health report:
- Health is strong
- Adoption continues to grow with the overall big data market
- Both user and dev communities continue to grow with increased usage
## Issues:
- There are no issues requiring board attention at this time
## LDAP committee group/Committership changes:
- Currently 23 committers and 20 LDAP committee group members
- No new LDAP committee group members added in the last 3 months
- Last LDAP committee group addition was Samarth Jain at Sat Mar 14 2015
- Josh Mahonin was added as a committer on Thu Jun 25 2015
## Releases:
- 4.4.0-HBase-0.98 was released on Wed May 20 2015
- 4.4.0-HBase-1.0 was released on Wed May 20 2015
- 4.4.0-HBase-1.1 was released on Thu May 28 2015
- 4.5.0-HBase-0.98 was released on Mon Jul 27 2015
- 4.5.0-HBase-1.0 was released on Wed Jul 29 2015
- 4.5.0-HBase-1.1 was released on Tue Jul 28 2015
## Mailing list activity:
- dev@phoenix.apache.org:
- 168 subscribers (up 22 in the last 3 months):
- 2736 emails sent to list (4972 in previous quarter)
- user@phoenix.apache.org:
- 359 subscribers (up 61 in the last 3 months):
- 671 emails sent to list (616 in previous quarter)
## JIRA activity:
- 214 JIRA tickets created in the last 3 months
- 144 JIRA tickets closed/resolved in the last 3 months
Report from the Apache Phoenix project [James R. Taylor]
## Description:
Apache Phoenix is a relational database layer on top of HBase.
## Activity:
- James Taylor and Maryann Xue gave a talk on Phoenix at HBaseCon.
- James Taylor represented Phoenix on a SQL-on-HBase panel at HBaseCon.
- James Taylor is scheduled to give a talk on Phoenix at Hadoop Summit
on June 10, 2015.
- Hortonworks hosted a Phoenix Meetup on May 5, 2015.
- Apache Ambari relies on Phoenix for its metrics system.
- Apache Yarn is planning on using Phoenix for its Application Timeline
service.
- Capital One has volunteered to host the next Phoenix meetup (date TBD).
- New Phoenix module added to integrate with Apache Spark
- New Phoenix module added to support testing on cluster at scale
## Issues:
- There are no issues requiring board attention at this time.
## PMC/Committership changes:
- Currently 22 committers and 20 PMC members in the project.
- New PMC members:
- Samarth Jain was added to the PMC on Sat Mar 14 2015
- Rajeshbabu Chintaguntla was added to the PMC on Sat Mar 14 2015
- Ravi Magham was added to the PMC on Sat Mar 14 2015
- Cody Marcel was added as a committer on Thu Apr 09 2015
## Releases:
- 4.3.1 was released on Tue Apr 07 2015
- 4.3.0 was released on Wed Feb 25 2015
- 3.3.0 was released on Wed Feb 25 2015
- 3.3.1 was released on Tue Apr 07 2015
## Mailing list activity:
- dev@phoenix.apache.org:
- 147 subscribers (up 28 in the last 3 months):
- 4976 emails sent to list (2962 in previous quarter)
- user@phoenix.apache.org:
- 301 subscribers (up 39 in the last 3 months):
- 620 emails sent to list (577 in previous quarter)
## JIRA activity:
- 315 JIRA tickets created in the last 3 months
- 251 JIRA tickets closed/resolved in the last 3 months
Phoenix is a relational database layer for accessing NoSQL datastores such as Apache HBase for low latency applications. It is accessed as a JDBC driver and supports querying and managing NoSQL tables using SQL. Releases: 2014-11-17 3.2.1 2014-11-17 4.2.1 2014-12-10 3.2.2 2014-12-10 4.2.2 Recent Activity: - Adopted new logo and improved website look-and-feel [1]. - Created "Who's using Phoenix" page with user/company quotes [2]. - Voting open on 3.3 and 4.3 releases. Notable features include map-reduce integration, many-to-many joins and functional indexes. - James will be presenting Apache Phoenix at the Hadoop Innovation Summit on 2015-02-13. - Created 202 JIRAs and resolved 208 in the past 3mo. PMC/Committers: Samarth Jain was elected as a committer on 2014-12-06. Thomas D'Silva was elected as a committer on 2015-02-09. Last PMC member was elected on 2014-04-08. Community: First ever Phoenix meetup scheduled for 2015-02-24. User list activity decreased 9% (197 -> 179 msg/mo) vs last 3mo Dev list activity decreased 4% (1052 -> 1005 msg/mo) vs last 3mo User subscribers increased 24% (211 -> 262 subscribers) vs last 3mo Dev subscribers increased 17% (102 -> 119 subscribers) vs last 3mo Board Issues: None [1] http://phoenix.apache.org/index.html [2] http://phoenix.apache.org/who_is_using.html
Phoenix is a relational database layer for accessing NoSQL datastores such as Apache HBase for low latency applications. It is accessed as a JDBC driver and supports querying and managing NoSQL tables using SQL. Releases: 2014-08-28 3.1.0 2014-08-28 4.1.0 2014-10-31 3.2.0 2014-10-31 4.2.0 Recent Activity: Last release introduces statistics collection to improve query performance and provide a foundation for cost-based query optimization. 258 JIRAs were created and 255 were resolved in the past three months. PMC/Committers: Ravi Magham (ravimagham) was elected as a committer on 2014-08-12. Last PMC member was elected on 2014-04-08. Community: User list activity increased 54% (128 -> 197 msg/mo) over previous three months Dev list activity increased 60% (636 -> 1052 msg/mo) over previous three months User subscribers increased 56% (135 -> 211 subscribers) from June Dev subscribers increased 41% (72 -> 102 subscribers) from June Board Issues: None
Phoenix is a SQL query engine for accessing NoSQL datastores such as Apache HBase. It is accessed as a JDBC driver and enables querying and managing NoSQL tables using SQL. Releases: 2014-04-03 3.0.0-incubating 2014-04-04 4.0.0-incubating 2014-08-11 Started vote on 3.1.0 release Recent Activity: Improved overall stability (77 JIRAs closed) and added several key new features for our current release being voted on: - Support for derived/nested queries to increase breadth of SQL support. - Added alternate, complementary "local" secondary indexing strategy. - Implemented the ability to trace distributed query execution. PMC: Last PMC member was elected on 2014-04-08. Committers: Two new committers have been added: 2014-07-19 Rajeshbabu Chintaguntla 2014-08-12 Ravi Kiran Mailing List Stats: User list activity is moderate with 132, 123, and 129 message in May, June, July Dev list activity is high with 591, 268, 1049 message in May June, July Board Issues: None
Phoenix is a SQL query engine for accessing NoSQL datastores such as Apache HBase. It is accessed as a JDBC driver and enables querying and managing NoSQL tables using SQL. * When did the project last make any releases? The latest release was version 4.0.0-incubating on 2014-04-04 * Describe the overall activity in the project over the past quarter. Conversion to TLP complete (kudos to INFRA on the quick turnaround). Both dev and user lists have occasional traffic. James Taylor gave a talk on Phoenix at the recent Hadoop Summit. Expect next release by end of July to include: - Support for derived/nested queries to increase breadth of SQL support. - Alternate, complementary secondary indexing strategy called local indexes. - Misc built-in functions contributed from various non committers. Work has started on reworking the type system so that it can be used when data is stored in HBase for projects such as HBase, Hive, Drill, Kite, and Impala. * When were the last committers or PMC members elected? The last PMC member was elected on 2014-04-08. Voting on two new committers is open. * Any issues for the Board? No
Phoenix is a SQL query engine for accessing NoSQL datastores such as Apache HBase. It is accessed as a JDBC driver and enables querying and managing NoSQL tables using SQL. * When did the project last make any releases? The latest release was version 4.0.0-incubating on 2014-04-04 * Describe the overall activity in the project over the past quarter. Conversion to TLP complete (kudos to INFRA on the quick turnaround). Both dev and user lists are busy. James Taylor gave a talk on Phoenix at Hadoop Summit. Expect next release by end of July to include: - Support for derived/nested queries to increase breadth of SQL support. - Alternate, complementary secondary indexing strategy called local indexes. - Misc built-in functions contributed from various non committers. Work has started on reworking the type system so that it can be used when data is stored in HBase for projects such as HBase, Hive, Drill, Kite, and Impala. * When were the last committers or PMC members elected? The last PMC member was elected on 2014-04-08. No new committers have been elected, but a vote on two new ones is expected to start shortly. * Any issues for the Board? No
Phoenix is an open source SQL query engine for accessing NoSQL data
stores such as Apache HBase. It is accessed as a JDBC driver and
enables querying and managing HBase tables using SQL.
Phoenix has been incubating since 12/11/2013.
Three most important issues to address in the move towards graduation:
1) Continue to make our users successful and prove the value of
Phoenix+HBase over other alternatives.
2) Continue to attract new users, contributors, and committers to the
project.
3) Become the defacto standard for accessing data stored in NoSQL stores.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
No
How has the community developed since the last report?
Both dev and user traffic is strong on the mailing list (780 and 187 mail
messages respectively). Work is underway by an engineer from Huawei to
add a new secondary indexing strategy called local indexing to Phoenix.
James Taylor gave a talk on Apache Phoenix at ApacheCon. Eli Levine and
James Taylor gave a talk on Phoenix at HBaseCon. James will also give a
talk at Hadoop Summit. Good discussions took place at the HBase
Hackathon on how to commonize the type system between Phoenix, HBase,
Hive, Impala, and Kite, as well as on how Continuity's transaction support
(soon to be open sourced) may be plugged into Phoenix. An interesting
discussion is underway on how Phoenix can be leveraged to get SQL
support for the Apache Accumulo project.
How has the project developed since the last report?
* Second release has been completed on 4/3/2014
* Third release has been completed on 4/4/2014
* Gabriel Reid was elected as a committer on 4/8/2014
* Graduation resolution passed on incubator general list on 5/4/2014.
Date of last release:
April 4, 2014
When were the last committers or PMC members elected?
Gabriel Reid was elected as a committer on 4/8/2014
Signed-off-by:
[X](phoenix) Michael Stack
[ ](phoenix) Steven Noels
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.
Phoenix has been incubating since 12/11/2013.
Three most important issues to address in the move towards graduation:
1) Make our customers successful and prove value of Phoenix+HBase over
other alternatives
2) Attract new committers and continue to get contributions from existing
committers to the project
3) Figure out a bundling strategy with HBase so that Phoenix is
pre-installed in HBase distributions.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
No
How has the community developed since the last report?
Continued growth of user/dev traffic on email list. James Taylor is giving
a talk on Apache Phoenix at ApacheCon.
How has the project developed since the last report?
* First release has been completed.
* Vote is in progress on general list for our second and third releases.
* Work in parallel on next point releases has already begun.
Date of last release:
March 13, 2014
When were the last committers or PMC members elected?
No new committers or PMC members, but a discussion has begun to add a new
committer
Signed-off-by:
[ ](phoenix) Lars Hofhansl
[X](phoenix) Andrew Purtell
[ ](phoenix) Devaraj Das
[ ](phoenix) Enis Soztutar
[ ](phoenix) Steven Noels
Shepherd/Mentor notes:
John Ament (johndament):
Phoenix is a newer podling, however they are growing quite fast. While
there were some release issues, those were resolved quite quickly on the
general list and new releases cut quickly. Based on this I would
strongly recommend that the podling consider graduation sooner than
later. Most of their status report is complete as well.
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. Phoenix has been incubating since 12/11/2013. Three most important issues to address in the move towards graduation: 1) Perform initial release out of apache incubator followed up quickly by two new releases 2) Make our customers successful and prove value of Phoenix+HBase over other alternatives 3) Attract new committers to the project Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? We've been waiting more than two months for our Github issues to be imported into our Apache JIRA. How has the community developed since the last report? Lots of user/dev traffic on email list and general interest. Received a nice patch from an external contributor to replace our CSV loader with the Apache Commons CSV loader that's under development. No new committers. How has the project developed since the last report? * IP Clearance is complete. * Vote is in progress on dev list for on our first release. Prior RC was sunk due to the license and notice files not being correct. * Working in parallel toward 3.0 and 4.0 releases as well. Date of last release: No release yet. When were the last committers or PMC members elected? No new committers or PMC members. Signed-off-by: [ ](phoenix) Lars Hofhansl [X](phoenix) Andrew Purtell [X](phoenix) Devaraj Das [ ](phoenix) Enis Soztutar [ ](phoenix) Steven Noels
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. Phoenix has been incubating since 12/11/2013. Three most important issues to address in the move towards graduation: 1) Perform initial release out of apache incubator followed up quickly by two new releases 2) Make our customers successful and prove value of Phoenix+HBase over other alternatives 3) Attract new committers to the project Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? The below is informational for the IPMC (no need to forward the board): We've been waiting for our Github issues to be imported into our Apache JIRA but it is taking a while. We're considering doing the import ourselves, as we're starting to see duplicate JIRAs and continue to have to point users back to our old Github issues. [[https://issues.apache.org/jira/browse/INFRA-7179|INFRA-7179]] How has the community developed since the last report? We've cut over from our former Github-based open source project to our new Apache home and dev and user lists are busy. No new committers. How has the project developed since the last report? * Apache Brand Management has ok'd our name of Apache Phoenix [1] * IP Clearance is nearly complete: software grant has been submitted and acknowledged. Vote is underway and will close on 2/8. IP-CLEARANCE note has been posted on general. * Reviewing proposed release on dev list and if all looks good, will start a vote for our first release next week. * Working in parallel toward a new 3.0.0 release as well. Date of last release: No release yet. When were the last committers or PMC members elected? No new committers or PMC members. 1. https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-44?filter=-2 Signed-off-by: [x](phoenix) Lars Hofhansl [X](phoenix) Andrew Purtell [X](phoenix) Devaraj Das [ ](phoenix) Enis Soztutar [X](phoenix) Steven Noels
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. Phoenix has been incubating since 12/11/2013. Three most important issues to address in the move towards graduation: 1) Get the necessary IP clearance from Salesforce to import and re-license existing open source project under phoenix.incubator.apache.org. 2) Get verification that our project name is acceptable [1]. 3) Perform first release out of apache incubator Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? This is our first report. No issues at this time. How has the community developed since the last report? - Questions are starting to come in on the apache dev and user mailing lists. - No new committers. How has the project developed since the last report? - The proposal committers have all been setup with Apache accounts. - Website is up [2] - Mailing lists and source repo have all set up (thanks to INFRA). - Working toward a 3.0.0 release in our existing open source project while we wait for on 1.) above. Date of last release: No release yet. When were the last committers or PMC members elected? No new committers or PMC members. [1] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-44?filter=-2 [2] http://phoenix.incubator.apache.org/ Signed-off-by: [x](phoenix) Lars Hofhansl [ ](phoenix) Andrew Purtell [x](phoenix) Devaraj Das [x](phoenix) Enis Soztutar [x](phoenix) Steven Noels