You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@phoenix.apache.org by ja...@apache.org on 2014/04/08 08:35:41 UTC
svn commit: r1585645 - in /incubator/phoenix/site: publish/roadmap.html
source/src/site/markdown/roadmap.md
Author: jamestaylor
Date: Tue Apr 8 06:35:40 2014
New Revision: 1585645
URL: http://svn.apache.org/r1585645
Log:
Update Roadmap to indicate port to 0.98 is complete
Modified:
incubator/phoenix/site/publish/roadmap.html
incubator/phoenix/site/source/src/site/markdown/roadmap.md
Modified: incubator/phoenix/site/publish/roadmap.html
URL: http://svn.apache.org/viewvc/incubator/phoenix/site/publish/roadmap.html?rev=1585645&r1=1585644&r2=1585645&view=diff
==============================================================================
--- incubator/phoenix/site/publish/roadmap.html (original)
+++ incubator/phoenix/site/publish/roadmap.html Tue Apr 8 06:35:40 2014
@@ -1,7 +1,7 @@
<!DOCTYPE html>
<!--
- Generated by Apache Maven Doxia at 2014-04-02
+ Generated by Apache Maven Doxia at 2014-04-08
Rendered using Reflow Maven Skin 1.1.0 (http://andriusvelykis.github.io/reflow-maven-skin)
-->
<html xml:lang="en" lang="en">
@@ -47,7 +47,7 @@
<a class="brand" href="index.html"><div class="xtoplogo"></div></a>
<div class="nav-collapse collapse" id="top-nav-collapse">
<ul class="nav pull-right">
- <li class="dropdown">
+ <li class="dropdown active">
<a href="#" class="dropdown-toggle" data-toggle="dropdown">About <b class="caret"></b></a>
<ul class="dropdown-menu">
<li ><a href="index.html" title="Overview">Overview</a></li>
@@ -59,7 +59,7 @@
<li ><a href="source.html" title="Source Repository">Source Repository</a></li>
<li ><a href="issues.html" title="Issue Tracking">Issue Tracking</a></li>
<li ><a href="download.html" title="Download">Download</a></li>
- <li class="divider"/>
+ <li ><a href="http:divider" title=""></a></li>
<li ><a href="http://www.apache.org/licenses/" title="License" class="externalLink">License</a></li>
<li ><a href="http://www.apache.org/foundation/sponsorship.html" title="Sponsorship" class="externalLink">Sponsorship</a></li>
<li ><a href="http://www.apache.org/foundation/thanks.html" title="Thanks" class="externalLink">Thanks</a></li>
@@ -74,7 +74,7 @@
<li ><a href="building.html" title="Building">Building</a></li>
<li ><a href="tuning.html" title="Tuning">Tuning</a></li>
<li ><a href="upgrade_from_2_2.html" title="Upgrade from 2.2">Upgrade from 2.2</a></li>
- <li class="divider"/>
+ <li ><a href="http:divider" title=""></a></li>
<li ><a href="secondary_indexing.html" title="Secondary Indexes">Secondary Indexes</a></li>
<li ><a href="joins.html" title="Joins">Joins</a></li>
<li ><a href="views.html" title="Views">Views</a></li>
@@ -86,7 +86,7 @@
<li ><a href="dynamic_columns.html" title="Dynamic Columns">Dynamic Columns</a></li>
<li ><a href="skip_scan.html" title="Skip Scan">Skip Scan</a></li>
<li ><a href="bulk_dataload.html" title="Bulk Loading">Bulk Loading</a></li>
- <li class="divider"/>
+ <li ><a href="http:divider" title=""></a></li>
<li ><a href="phoenix_on_emr.html" title="Amazon EMR Support">Amazon EMR Support</a></li>
<li ><a href="flume.html" title="Apache Flume Plugin">Apache Flume Plugin</a></li>
<li ><a href="pig_integration.html" title="Apache Pig Integration">Apache Pig Integration</a></li>
@@ -128,6 +128,7 @@
<li><b><a href="multi_tenancy.html">Multi-tenancy</a></b>. Allows independent views to be created by different tenants on a per-connection basis that all share the same physical HBase table. <b>Available in 3.0/4.0 release</b></li>
<li><b><a href="sequences.html">Sequences</a></b>. Support the atomic increment of sequence values through the CREATE SEQUENCE, the NEXT VALUE FOR, and the CURRENT VALUE FOR statements. <b>Available in 3.0/4.0 release</b></li>
<li><b><a href="array_type.html">ARRAY Type</a></b>. Support for the standard JDBC ARRAY type. <b>Available in 3.0/4.0 release</b></li>
+ <li><b><a class="externalLink" href="https://issues.apache.org/jira/browse/PHOENIX-480">Port to HBase 0.98</a></b>. Enable Phoenix to work with HBase 0.98. <b>Available in our 4.0 release</b></li>
<li><b>Type Enhancements</b>. Additional work includes support for <a class="externalLink" href="https://issues.apache.org/jira/browse/PHOENIX-476">DEFAULT declaration</a> when creating a table, and for <a class="externalLink" href="https://issues.apache.org/jira/browse/PHOENIX-477">STRUCT</a> and <a class="externalLink" href="https://issues.apache.org/jira/browse/PHOENIX-628">JSON</a> data types.</li>
<li><b>Third Party Integration</b>. There are a number of open source projects with which interop with Phoenix could be added or improved:
<ul>
@@ -143,7 +144,6 @@
<li><b><a class="externalLink" href="https://issues.apache.org/jira/browse/PHOENIX-177">Monitoring and Management</a></b>. Provide visibility into cpu, physical io, logical io, wait time, blocking time, and transmission time spent for each thread of execution across the HBase cluster, within coprocessors, and within the client-side thread pools for each query. On top of this, we should exposing things like active sessions and currently running queries. The <a class="externalLink" href="http://phoenix.incubator.apache.org/language/index.html#/explain">EXPLAIN PLAN</a> gives an idea of how a query will be executed, but we need more information to help users debug and tune their queries.</li>
<li><b><a class="externalLink" href="https://issues.apache.org/jira/browse/PHOENIX-150">Parent/child Join</a></b>. Unlike with standard relational databases, HBase allows you the flexibility of dynamically creating as many key values in a row as youâd like. Phoenix could leverage this by providing a way to model child rows inside of a parent row. The child row would be comprised of the set of key values whose column qualifier is prefixed with a known name and appended with the primary key of the child row. Phoenix could hide all this complexity, and allow querying over the nested children through joining to the parent row. Essentially, this would be an optimization of the general join case, but could support cases where both sides of the join are bigger than would fit into memory.</li>
<li><b><a class="externalLink" href="https://issues.apache.org/jira/browse/PHOENIX-716">Intra-row secondary indexes</a></b>. Once we support putting multiple âvirtualâ rows inside of a HBase row as prefixed KeyValues, we can support intra-row secondary indexes without much more effort.</li>
- <li><b><a class="externalLink" href="https://issues.apache.org/jira/browse/PHOENIX-480">Port to HBase 0.96</a></b>. Currently Phoenix only works on the 0.94 branch of HBase. The latest branch of HBase is now 0.96, which has many breaking, non backward compatible changes (for example requiring that EndPoint coprocessors use protobufs). Ideally, we should create a shim thatâll allow Phoenix to work with both 0.94 and 0.96, but barring that, we should have a branch of Phoenix that works under 0.96. Additional work includes replacing our type system with the new HBase type system in 0.96, but that would be significantly more work.</li>
<li><b>Security Features</b>. A number of existing HBase security features in 0.94 could be leverage and new security features being added to 0.98 could be leveraged in the future.
<ul>
<li><b><a class="externalLink" href="https://issues.apache.org/jira/browse/PHOENIX-672">Support GRANT and REVOKE</a></b>. Support the standard GRANT and REVOKE SQL commands through an HBase AccessController.</li>
Modified: incubator/phoenix/site/source/src/site/markdown/roadmap.md
URL: http://svn.apache.org/viewvc/incubator/phoenix/site/source/src/site/markdown/roadmap.md?rev=1585645&r1=1585644&r2=1585645&view=diff
==============================================================================
--- incubator/phoenix/site/source/src/site/markdown/roadmap.md (original)
+++ incubator/phoenix/site/source/src/site/markdown/roadmap.md Tue Apr 8 06:35:40 2014
@@ -9,6 +9,7 @@ Our roadmap is driven by our user commun
3. **[Multi-tenancy](multi_tenancy.html)**. Allows independent views to be created by different tenants on a per-connection basis that all share the same physical HBase table. **Available in 3.0/4.0 release**
4. **[Sequences](sequences.html)**. Support the atomic increment of sequence values through the CREATE SEQUENCE, the NEXT VALUE FOR, and the CURRENT VALUE FOR statements. **Available in 3.0/4.0 release**
5. **[ARRAY Type](array_type.html)**. Support for the standard JDBC ARRAY type. **Available in 3.0/4.0 release**
+6. **[Port to HBase 0.98](https://issues.apache.org/jira/browse/PHOENIX-480)**. Enable Phoenix to work with HBase 0.98. **Available in our 4.0 release**
6. **Type Enhancements**. Additional work includes support for [DEFAULT declaration](https://issues.apache.org/jira/browse/PHOENIX-476) when creating a table, and for [STRUCT](https://issues.apache.org/jira/browse/PHOENIX-477) and [JSON](https://issues.apache.org/jira/browse/PHOENIX-628) data types.
7. **Third Party Integration**. There are a number of open source projects with which interop with Phoenix could be added or improved:
* **[Apache Flume sink](https://issues.apache.org/jira/browse/PHOENIX-356)**. Support a Flume sink that writes Phoenix-compliant HBase data. **Available in 3.0/4.0 release**
@@ -22,7 +23,6 @@ Our roadmap is driven by our user commun
10. **[Monitoring and Management](https://issues.apache.org/jira/browse/PHOENIX-177)**. Provide visibility into cpu, physical io, logical io, wait time, blocking time, and transmission time spent for each thread of execution across the HBase cluster, within coprocessors, and within the client-side thread pools for each query. On top of this, we should exposing things like active sessions and currently running queries. The [EXPLAIN PLAN](http://phoenix.incubator.apache.org/language/index.html#/explain) gives an idea of how a query will be executed, but we need more information to help users debug and tune their queries.
11. **[Parent/child Join](https://issues.apache.org/jira/browse/PHOENIX-150)**. Unlike with standard relational databases, HBase allows you the flexibility of dynamically creating as many key values in a row as you'd like. Phoenix could leverage this by providing a way to model child rows inside of a parent row. The child row would be comprised of the set of key values whose column qualifier is prefixed with a known name and appended with the primary key of the child row. Phoenix could hide all this complexity, and allow querying over the nested children through joining to the parent row. Essentially, this would be an optimization of the general join case, but could support cases where both sides of the join are bigger than would fit into memory.
12. **[Intra-row secondary indexes](https://issues.apache.org/jira/browse/PHOENIX-716)**. Once we support putting multiple "virtual" rows inside of a HBase row as prefixed KeyValues, we can support intra-row secondary indexes without much more effort.
-13. **[Port to HBase 0.96](https://issues.apache.org/jira/browse/PHOENIX-480)**. Currently Phoenix only works on the 0.94 branch of HBase. The latest branch of HBase is now 0.96, which has many breaking, non backward compatible changes (for example requiring that EndPoint coprocessors use protobufs). Ideally, we should create a shim that'll allow Phoenix to work with both 0.94 and 0.96, but barring that, we should have a branch of Phoenix that works under 0.96. Additional work includes replacing our type system with the new HBase type system in 0.96, but that would be significantly more work.
14. **Security Features**. A number of existing HBase security features in 0.94 could be leverage and new security features being added to 0.98 could be leveraged in the future.
* **[Support GRANT and REVOKE](https://issues.apache.org/jira/browse/PHOENIX-672)**. Support the standard GRANT and REVOKE SQL commands through an HBase AccessController.
* **[Surface support for encryption] (https://issues.apache.org/jira/browse/PHOENIX-673)**. In HBase 0.98, transparent encryption will be possible. We should surface this in Phoenix.