You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@phoenix.apache.org by mu...@apache.org on 2014/01/21 02:18:31 UTC
svn commit: r1559875 - in /incubator/phoenix/site/publish: download.html
recent.html roadmap.html
Author: mujtaba
Date: Tue Jan 21 01:18:30 2014
New Revision: 1559875
URL: http://svn.apache.org/r1559875
Log:
Update recent, download and roadmap page
Modified:
incubator/phoenix/site/publish/download.html
incubator/phoenix/site/publish/recent.html
incubator/phoenix/site/publish/roadmap.html
Modified: incubator/phoenix/site/publish/download.html
URL: http://svn.apache.org/viewvc/incubator/phoenix/site/publish/download.html?rev=1559875&r1=1559874&r2=1559875&view=diff
==============================================================================
--- incubator/phoenix/site/publish/download.html (original)
+++ incubator/phoenix/site/publish/download.html Tue Jan 21 01:18:30 2014
@@ -1,7 +1,7 @@
<!DOCTYPE html>
<!--
- Generated by Apache Maven Doxia at Jan 14, 2014
+ Generated by Apache Maven Doxia at Jan 20, 2014
Rendered using Maven Reflow Skin 1.0.0 (http://andriusvelykis.github.com/reflow-maven-skin)
-->
<html xml:lang="en" lang="en">
@@ -175,6 +175,68 @@
<div class="section">
<h3 id="Samples">Samples</h3>
<p>The best place to see samples are in our unit tests under src/test/java. The ones in the endToEnd package are tests demonstrating how to use all aspects of the Phoenix JDBC driver. We also have some examples in the examples directory.</p>
+ </div>
+ <div class="section">
+ <h3 id="Phoenix_Client_-_Server_Compatibility">Phoenix Client - Server Compatibility</h3>
+ <p>Major and minor version should match between client and server (patch version can mismatch). Following is the list of compatible client and server version(s). It is recommended that same client and server version are used. </p>
+ <table border="0" class="bodyTable table table-striped table-hover">
+ <thead>
+ <tr class="a">
+ <th>Phoenix Client Version </th>
+ <th>Compatible Server Versions</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr class="b">
+ <td>1.0.0 </td>
+ <td>1.0.0</td>
+ </tr>
+ <tr class="a">
+ <td>1.1.0 </td>
+ <td>1.1.0</td>
+ </tr>
+ <tr class="b">
+ <td>1.2.0 </td>
+ <td>1.2.0, 1.2.1</td>
+ </tr>
+ <tr class="a">
+ <td>1.2.1 </td>
+ <td>1.2.0, 1.2.1</td>
+ </tr>
+ <tr class="b">
+ <td>2.0.0 </td>
+ <td>2.0.0, 2.0.1, 2.0.2</td>
+ </tr>
+ <tr class="a">
+ <td>2.0.1 </td>
+ <td>2.0.0, 2.0.1, 2.0.2</td>
+ </tr>
+ <tr class="b">
+ <td>2.0.2 </td>
+ <td>2.0.0, 2.0.1, 2.0.2</td>
+ </tr>
+ <tr class="a">
+ <td>2.1.0 </td>
+ <td>2.1.0, 2.1.1, 2.1.2</td>
+ </tr>
+ <tr class="b">
+ <td>2.1.1 </td>
+ <td>2.1.0, 2.1.1, 2.1.2</td>
+ </tr>
+ <tr class="a">
+ <td>2.1.2 </td>
+ <td>2.1.0, 2.1.1, 2.1.2</td>
+ </tr>
+ <tr class="b">
+ <td>2.2.0 </td>
+ <td>2.2.0, 2.2.1</td>
+ </tr>
+ <tr class="a">
+ <td>2.2.1 </td>
+ <td>2.2.0, 2.2.1</td>
+ </tr>
+ </tbody>
+ </table>
<p><a class="externalLink" href="http://githalytics.com/forcedotcom/phoenix.git"><img src="https://cruel-carlota.pagodabox.com/33878dc7c0522eed32d2d54db9c59f78" alt="githalytics.com alpha" /></a></p>
</div>
</div>
@@ -313,7 +375,7 @@
<div class="span12">
<p class="pull-right"><a href="#">Back to top</a></p>
<p class="copyright">Copyright ©2014 <a href="http://www.apache.org">Apache Software Foundation</a>. All Rights Reserved.</p>
- <p class="version-date"><span class="projectVersion">Version: 2.2.3. </span><span class="publishDate">Last Published: 2014-01-14. </span></p>
+ <p class="version-date"><span class="projectVersion">Version: 2.2.3. </span><span class="publishDate">Last Published: 2014-01-20. </span></p>
</div>
</div>
</div>
Modified: incubator/phoenix/site/publish/recent.html
URL: http://svn.apache.org/viewvc/incubator/phoenix/site/publish/recent.html?rev=1559875&r1=1559874&r2=1559875&view=diff
==============================================================================
--- incubator/phoenix/site/publish/recent.html (original)
+++ incubator/phoenix/site/publish/recent.html Tue Jan 21 01:18:30 2014
@@ -1,7 +1,7 @@
<!DOCTYPE html>
<!--
- Generated by Apache Maven Doxia at Jan 14, 2014
+ Generated by Apache Maven Doxia at Jan 20, 2014
Rendered using Maven Reflow Skin 1.0.0 (http://andriusvelykis.github.com/reflow-maven-skin)
-->
<html xml:lang="en" lang="en">
@@ -114,6 +114,7 @@
<p>As items are implemented from our road map, they are moved here to track the progress weve made:</p>
<ol style="list-style-type: decimal">
<li><b>Joins</b>. Join support through hash joins (where one side of the query is small enough to fit into memory) is now available in our master branch.</li>
+ <li><b><a class="externalLink" href="http://phoenix.incubator.apache.org/sequences.html">Sequences</a></b>. Support for CREATE/DROP SEQUENCE, NEXT VALUE FOR, and CURRENT VALUE FOR has been implemented and is now available in our master branch.</li>
<li><b>Multi-tenancy</b>. Support for creating multi-tenant tables is now available in our master branch.</li>
<li><b><a href="secondary_indexing.html">Secondary Indexes</a></b>. Allows users to create indexes over mutable or immutable data through a new <tt>CREATE INDEX</tt> DDL command. Behind the scenes, Phoenix creates a separate HBase table with a different row key for the index. At query time, Phoenix takes care of choosing the best table to use based on how much of the row key can be formed. We support getting at the uncommitted <tt>List<KeyValue></tt> for both the data and the index tables to allow an HFile to be built without needing an HBase connection using the connectionless of our JDBC driver.</li>
<li><b>Row Value Constructors</b>. A standard SQL construct to efficiently locate the row at or after a composite key value. Enables a query-more capability to efficiently step through your data and optimizes IN list of composite key values to be point gets.</li>
@@ -262,7 +263,7 @@
<div class="span12">
<p class="pull-right"><a href="#">Back to top</a></p>
<p class="copyright">Copyright ©2014 <a href="http://www.apache.org">Apache Software Foundation</a>. All Rights Reserved.</p>
- <p class="version-date"><span class="projectVersion">Version: 2.2.3. </span><span class="publishDate">Last Published: 2014-01-14. </span></p>
+ <p class="version-date"><span class="projectVersion">Version: 2.2.3. </span><span class="publishDate">Last Published: 2014-01-20. </span></p>
</div>
</div>
</div>
Modified: incubator/phoenix/site/publish/roadmap.html
URL: http://svn.apache.org/viewvc/incubator/phoenix/site/publish/roadmap.html?rev=1559875&r1=1559874&r2=1559875&view=diff
==============================================================================
--- incubator/phoenix/site/publish/roadmap.html (original)
+++ incubator/phoenix/site/publish/roadmap.html Tue Jan 21 01:18:30 2014
@@ -1,7 +1,7 @@
<!DOCTYPE html>
<!--
- Generated by Apache Maven Doxia at Jan 14, 2014
+ Generated by Apache Maven Doxia at Jan 20, 2014
Rendered using Maven Reflow Skin 1.0.0 (http://andriusvelykis.github.com/reflow-maven-skin)
-->
<html xml:lang="en" lang="en">
@@ -117,44 +117,17 @@
<h4 id="Note:_Issues_on_Github_would_be_converted_to_JIRAs_soon.">Note: Issues on Github would be converted to JIRAs soon.</h4>
<p>Our roadmap is driven by our user community. Below, in prioritized order, is the current plan for Phoenix:</p>
<ol style="list-style-type: decimal">
- <li><b>Hash Joins</b>. Provide the ability to join together multiple tables, through a phased approach:</li>
- </ol>
- <ul>
- <li><b><a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/20">Equi-join</a></b>. Support left, right, inner, outer equi-joins where one side of the join is small enough to fit into memory. <b>Available in master branch</b></li>
- <li><b><a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/36">Semi/anti-join</a></b>. Support correlated sub queries for exists and in where one side of the join is small enough to fit into memory.</li>
- </ul>
- <ol style="list-style-type: decimal">
+ <li><b>Hash Joins</b>. Provide the ability to join together multiple tables, through a phased approach: <br /><b><a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/20">Equi-join</a></b>. Support left, right, inner, outer equi-joins where one side of the join is small enough to fit into memory. <b>Available in master branch</b> <br /><b><a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/36">Semi/anti-join</a></b>. Support correlated sub queries for exists and in where one side of the join is small enough to fit into memory.</li>
<li><b><a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/296">Multi-tenant Tables</a></b>. Allows the creation of multiple tables from a base tables on the same physical HBase table. <b>Available in master branch</b></li>
- <li><b><a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/18?source=c">Sequences</a></b>. Support the atomic increment of sequence values through the CREATE SEQUENCE and the NEXT VALUE FOR statements.</li>
+ <li><b><a class="externalLink" href="http://phoenix.incubator.apache.org/sequences.html">Sequences</a></b>. Support the atomic increment of sequence values through the CREATE SEQUENCE and the NEXT VALUE FOR statements.</li>
<li><b>Type Enhancements</b>. Additional work includes support for <a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/345">DEFAULT declaration</a> when creating a table, for <a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/178">ARRAY</a> (<b>available in master branch</b>), <a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/346">STRUCT</a>, and <a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/497">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:</li>
- </ol>
- <ul>
- <li><b><a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/225">Flume sink</a></b>. Support a Flume sink that writes Phoenix-compliant HBase data. <b>Available in master branch</b></li>
- <li><b><a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/224">Hue integration</a></b>. Add Phoenix as an HBase service layer in Hue.</li>
- <li><b><a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/512">Pentaho Mondrian support</a></b>. Allow Phoenix to be used as the JDBC driver for Pentaho Mondrian. <b>This effort is pretty far along already, with the Pentaho FoodMart demo running through Phoenix now</b></li>
- <li><b><a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/499">Cleanup Pig support</a></b> . Commonize the functions we use across Map-reduce and Pig processing. We should also upgrade our pom to reference the 0.12 version of Pig and map our DECIMAL type to their new decimal type.</li>
- <li><b><a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/556">Improve Map-reduce integration</a></b>. Its possible that we could provide a processing model where the map and reduce functions can invoke Phoenix queries (though this needs some more thought).</li>
- </ul>
- <ol style="list-style-type: decimal">
+ <li><b>Third Party Integration</b>. There are a number of open source projects with which interop with Phoenix could be added or improved: <br /> <b><a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/225">Flume sink</a></b>. Support a Flume sink that writes Phoenix-compliant HBase data. <b>Available in master branch</b> <br /> <b><a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/224">Hue integration</a></b>. Add Phoenix as an HBase service layer in Hue. <br /> <b><a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/512">Pentaho Mondrian support</a></b>. Allow Phoenix to be used as the JDBC driver for Pentaho Mondrian. <b>This effort is pretty far along already, with the Pentaho FoodMart demo running through Phoenix now</b> <br /> <b><a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/499">Cleanup Pig support</a></b> . Commonize the functions we use across Map-reduce and Pig processi
ng. We should also upgrade our pom to reference the 0.12 version of Pig and map our DECIMAL type to their new decimal type. <br /> <b><a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/556">Improve Map-reduce integration</a></b>. Its possible that we could provide a processing model where the map and reduce functions can invoke Phoenix queries (though this needs some more thought).</li>
<li><b><a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/5">Derived Tables</a></b>. Allow a <tt>SELECT</tt> clause to be used in the FROM clause to define a derived table. This would include support for pipelining queries when necessary.</li>
<li><b><a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/383">Functional Indexes</a></b>. Enables an index to contain the evaluation of an expression as opposed to just a column value.</li>
<li><b><a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/46">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://forcedotcom.github.io/phoenix/#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://github.com/forcedotcom/phoenix/issues/19">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 youd 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>
- </ol>
- <ul>
- <li><b><a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/585">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>
- </ul>
- <ol style="list-style-type: decimal">
+ <li><b><a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/19">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 youd 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. <br /> <b><a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/585">Intra-row secondary indexes</a></b>. Once we support putting multiple virtual rows inside of a HBase row as pref
ixed KeyValues, we can support intra-row secondary indexes without much more effort.</li>
<li><b><a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/349">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 thatll 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.</li>
- </ol>
- <ul>
- <li><b><a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/541">Support GRANT and REVOKE</a></b>. Support the standard GRANT and REVOKE SQL commands through an HBase AccessController.</li>
- <li><b><a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/542">Surface support for encryption</a></b>. In HBase 0.98, transparent encryption will be possible. We should surface this in Phoenix.</li>
- <li><b><a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/553">Support Cell-level security</a></b>. In HBase 0.98, it will be possible to apply labels at a per-cell granularity. We should surface this in Phoenix.</li>
- </ul>
- <ol style="list-style-type: decimal">
+ <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. <br /> <b><a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/541">Support GRANT and REVOKE</a></b>. Support the standard GRANT and REVOKE SQL commands through an HBase AccessController. <br /> <b><a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/542">Surface support for encryption</a></b>. In HBase 0.98, transparent encryption will be possible. We should surface this in Phoenix. <br /> <b><a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/553">Support Cell-level security</a></b>. In HBase 0.98, it will be possible to apply labels at a per-cell granularity. We should surface this in Phoenix.</li>
<li><b>Cost-based Optimizer</b>. Once secondary indexing and joins are implemented, well need to <a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/64">collect and maintains stats</a> and <a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/49">drive query optimization decisions based on them</a> to produce the most efficient query plan.</li>
<li><b><a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/459">Query over Multiple Row Versions</a></b>. Expose the time dimension of rows through a built-in function to allow aggregation and trending over multiple row versions.</li>
<li><b><a class="externalLink" href="https://github.com/forcedotcom/phoenix/issues/23">OLAP Extensions</a></b>. Support the <tt>WINDOW</tt>, <tt>PARTITION OVER</tt>, <tt>RANK</tt>, etc. functionality.</li>
@@ -301,7 +274,7 @@
<div class="span12">
<p class="pull-right"><a href="#">Back to top</a></p>
<p class="copyright">Copyright ©2014 <a href="http://www.apache.org">Apache Software Foundation</a>. All Rights Reserved.</p>
- <p class="version-date"><span class="projectVersion">Version: 2.2.3. </span><span class="publishDate">Last Published: 2014-01-14. </span></p>
+ <p class="version-date"><span class="projectVersion">Version: 2.2.3. </span><span class="publishDate">Last Published: 2014-01-20. </span></p>
</div>
</div>
</div>