Author: jamestaylor
Date: Thu Dec  1 23:21:15 2016
New Revision: 1772290

URL: http://svn.apache.org/viewvc?rev=1772290&view=rev
Log:
Add recently implemented features and remove them from the roadmap

Modified:
    phoenix/site/publish/recent.html
    phoenix/site/publish/roadmap.html
    phoenix/site/source/src/site/markdown/recent.md
    phoenix/site/source/src/site/markdown/roadmap.md

Modified: phoenix/site/publish/recent.html
URL: 
http://svn.apache.org/viewvc/phoenix/site/publish/recent.html?rev=1772290&r1=1772289&r2=1772290&view=diff
==============================================================================
--- phoenix/site/publish/recent.html (original)
+++ phoenix/site/publish/recent.html Thu Dec  1 23:21:15 2016
@@ -1,7 +1,7 @@
 
 <!DOCTYPE html>
 <!--
- Generated by Apache Maven Doxia at 2016-11-30
+ Generated by Apache Maven Doxia at 2016-12-01
  Rendered using Reflow Maven Skin 1.1.0 
(http://andriusvelykis.github.io/reflow-maven-skin)
 -->
 <html  xml:lang="en" lang="en">
@@ -154,6 +154,8 @@
 </div> 
 <p>As items are implemented from our road map, they are moved here to track 
the progress we’ve made:</p> 
 <ol style="list-style-type: decimal"> 
+ <li><b><a class="externalLink" 
href="https://phoenix.apache.org/atomic_upsert.html";>Atomic update</a></b>. 
Atomic update is now possible in the UPSERT VALUES statement in support of 
counters and other use cases. <b>Available in our 4.9 release</b></li> 
+ <li><b><a class="externalLink" 
href="https://phoenix.apache.org/language/index.html#column_def";>DEFAULT 
declaration</a></b>. When defining a column it is now possible to provide a 
DEFAULT declaration for the initial value. <b>Available in our 4.9 
release</b></li> 
  <li><b><a class="externalLink" 
href="https://issues.apache.org/jira/browse/PHOENIX-1311";>Namespace 
Mapping</a></b>. Maps Phoenix schema to HBase namespace to improve isolation 
between different schemas. <b>Available in our 4.8 release</b></li> 
  <li><b><a class="externalLink" 
href="https://issues.apache.org/jira/browse/PHOENIX-2743";>Hive 
Integration</a></b>. Enables Hive to be used with Phoenix in support of joining 
huge tables to other huge tables. <b>Available in our 4.8 release</b></li> 
  <li><b><a class="externalLink" 
href="https://issues.apache.org/jira/browse/PHOENIX-1734";>Local Index 
Improvements</a></b>. Reworked local index implementation to guarantee 
colocation of table and index data and use supported HBase APIs for better 
maintainability. <b>Available in our 4.8 release</b></li> 

Modified: phoenix/site/publish/roadmap.html
URL: 
http://svn.apache.org/viewvc/phoenix/site/publish/roadmap.html?rev=1772290&r1=1772289&r2=1772290&view=diff
==============================================================================
--- phoenix/site/publish/roadmap.html (original)
+++ phoenix/site/publish/roadmap.html Thu Dec  1 23:21:15 2016
@@ -1,7 +1,7 @@
 
 <!DOCTYPE html>
 <!--
- Generated by Apache Maven Doxia at 2016-11-30
+ Generated by Apache Maven Doxia at 2016-12-01
  Rendered using Reflow Maven Skin 1.1.0 
(http://andriusvelykis.github.io/reflow-maven-skin)
 -->
 <html  xml:lang="en" lang="en">
@@ -156,7 +156,6 @@
 <ol style="list-style-type: decimal"> 
  <li><b><a class="externalLink" 
href="https://issues.apache.org/jira/browse/PHOENIX-3146";>Stress 
testing</a></b>. Open source and automate the running of stress tests that 
exercise Phoenix and HBase under high load.</li> 
  <li><b><a class="externalLink" 
href="https://issues.apache.org/jira/browse/PHOENIX-3183";>Compatibility 
testing</a></b>. Open source and automate the running of backward compatibility 
tests for Phoenix and HBase, including new server versions of Phoenix working 
with older client versions and unreleased HBase versions compiling with 
existing Phoenix versions.</li> 
- <li><b><a class="externalLink" 
href="https://issues.apache.org/jira/browse/PHOENIX-2909";>Atomic 
update</a></b>. Support an UPDATE statement that runs atomically for a row 
updates of non transactional tables as a means to expose check-and-put and 
increment functionality for Phoenix.</li> 
  <li><b><a class="externalLink" 
href="https://issues.apache.org/jira/browse/PHOENIX-1598";>Column 
encoding</a></b>. Providing an indirection between the column name and the 
column qualifier reduces storage space, improves performance and opens the door 
for enhancements such as renaming columns and dropping columns 
asynchronously.</li> 
  <li><b><a class="externalLink" 
href="https://issues.apache.org/jira/browse/PHOENIX-2565";>Immutable data 
packing</a></b>. Since columns in immutable tables are not updated 
individually, but only inserted together, we can pack all values in a single 
cell to reduce storage space and improve performance.</li> 
  <li><b><a class="externalLink" 
href="https://calcite.incubator.apache.org/";>Apache Calcite adapter</a></b>. 
Create a Phoenix adapter for Calcite to increase the breadth of our SQL 
support, plug into a rich cost-based optimizer framework, and enable potential 
interop with other adapters. <b>See our <a class="externalLink" 
href="https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=shortlog;h=refs/heads/calcite";>calcite
 branch</a> to try this and track our progress.</b></li> 
@@ -170,7 +169,6 @@
    <li><b><a class="externalLink" 
href="https://issues.apache.org/jira/browse/PHOENIX-150";>Inlined parent/child 
joins</a></b>. Optimize parent/child joins by storing child rows inside of a 
parent row, forming the column qualifier through a known prefix plus the child 
row primary key.</li> 
   </ul></li> 
  <li><b><a href="subqueries.html">Subquery enhancements</a></b>, which 
includes support for <b><a class="externalLink" 
href="https://issues.apache.org/jira/browse/PHOENIX-1388";>correlated subqueries 
in the HAVING clause</a></b> and <b><a class="externalLink" 
href="https://issues.apache.org/jira/browse/PHOENIX-1392";>using subqueries as 
expressions</a></b>.</li> 
- <li><b><a class="externalLink" 
href="https://issues.apache.org/jira/browse/PHOENIX-476";>DEFAULT 
declaration</a></b>. When creating a table, we should allow a DEFAULT 
declaration in our CREATE TABLE statement.</li> 
  <li><b><a class="externalLink" 
href="https://issues.apache.org/jira/browse/PHOENIX-477";>STRUCT type</a></b>. 
Allow declarations of multiple fields of different data types that would be 
packed into a single cell to reduce the per column storage overhead.</li> 
  <li><b><a class="externalLink" 
href="https://issues.apache.org/jira/browse/PHOENIX-154";>OLAP 
Extensions</a></b>. Support the <tt>WINDOW</tt>, <tt>PARTITION OVER</tt>, 
<tt>RANK</tt>, and other SQL-92 extensions.</li> 
  <li><b><a class="externalLink" 
href="https://issues.apache.org/jira/browse/PHOENIX-590";>Multi-version Row 
Queries</a></b>. Expose the time dimension of rows through a built-in function 
to allow aggregation and trending over multiple row versions.</li> 

Modified: phoenix/site/source/src/site/markdown/recent.md
URL: 
http://svn.apache.org/viewvc/phoenix/site/source/src/site/markdown/recent.md?rev=1772290&r1=1772289&r2=1772290&view=diff
==============================================================================
--- phoenix/site/source/src/site/markdown/recent.md (original)
+++ phoenix/site/source/src/site/markdown/recent.md Thu Dec  1 23:21:15 2016
@@ -2,6 +2,8 @@
 
 As items are implemented from our road map, they are moved here to track the 
progress we've made:
 
+1. **[Atomic update](https://phoenix.apache.org/atomic_upsert.html)**. Atomic 
update is now possible in the UPSERT VALUES statement in support of counters 
and other use cases. **Available in our 4.9  release**
+6. **[DEFAULT 
declaration](https://phoenix.apache.org/language/index.html#column_def)**. When 
defining a column it is now possible to provide a DEFAULT declaration for the 
initial value. **Available in our 4.9  release**
 1. **[Namespace 
Mapping](https://issues.apache.org/jira/browse/PHOENIX-1311)**. Maps Phoenix 
schema to HBase namespace to improve isolation between different schemas. 
**Available in our 4.8  release**
 1. **[Hive Integration](https://issues.apache.org/jira/browse/PHOENIX-2743)**. 
Enables Hive to be used with Phoenix in support of joining huge tables to other 
huge tables. **Available in our 4.8  release**
 1. **[Local Index 
Improvements](https://issues.apache.org/jira/browse/PHOENIX-1734)**. Reworked 
local index implementation to guarantee colocation of table and index data and 
use supported HBase APIs for better maintainability. **Available in our 4.8  
release**

Modified: phoenix/site/source/src/site/markdown/roadmap.md
URL: 
http://svn.apache.org/viewvc/phoenix/site/source/src/site/markdown/roadmap.md?rev=1772290&r1=1772289&r2=1772290&view=diff
==============================================================================
--- phoenix/site/source/src/site/markdown/roadmap.md (original)
+++ phoenix/site/source/src/site/markdown/roadmap.md Thu Dec  1 23:21:15 2016
@@ -4,7 +4,6 @@ Our roadmap is driven by our user commun
 
 1. **[Stress testing](https://issues.apache.org/jira/browse/PHOENIX-3146)**. 
Open source and automate the running of stress tests that exercise Phoenix and 
HBase under high load.
 1. **[Compatibility 
testing](https://issues.apache.org/jira/browse/PHOENIX-3183)**. Open source and 
automate the running of backward compatibility tests for Phoenix and HBase, 
including new server versions of Phoenix working with older client versions and 
unreleased HBase versions compiling with existing Phoenix versions.
-1. **[Atomic update](https://issues.apache.org/jira/browse/PHOENIX-2909)**. 
Support an UPDATE statement that runs atomically for a row updates of non 
transactional tables as a means to expose check-and-put and increment 
functionality for Phoenix.
 1. **[Column encoding](https://issues.apache.org/jira/browse/PHOENIX-1598)**. 
Providing an indirection between the column name and the column qualifier 
reduces storage space, improves performance and opens the door for enhancements 
such as renaming columns and dropping columns asynchronously.
 1. **[Immutable data 
packing](https://issues.apache.org/jira/browse/PHOENIX-2565)**. Since columns 
in immutable tables are not updated individually, but only inserted together, 
we can pack all values in a single cell to reduce storage space and improve 
performance.
 1. **[Apache Calcite adapter](https://calcite.incubator.apache.org/)**. Create 
a Phoenix adapter for Calcite to increase the breadth of our SQL support, plug 
into a rich cost-based optimizer framework, and enable potential interop with 
other adapters. **See our [calcite 
branch](https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=shortlog;h=refs/heads/calcite)
 to try this and track our progress.**
@@ -14,7 +13,6 @@ Our roadmap is driven by our user commun
     *  **[Table-stats-guided choice between hash join and sort-merge 
join](https://issues.apache.org/jira/browse/PHOENIX-1556)**. Base hash join 
versus many-to-many decision on how many guideposts will be traversed for RHS 
table(s).
     *  **[Inlined parent/child 
joins](https://issues.apache.org/jira/browse/PHOENIX-150)**. Optimize 
parent/child joins by storing child rows inside of a parent row, forming the 
column qualifier through a known prefix plus the child row primary key.
 2. **[Subquery enhancements](subqueries.html)**, which includes support for 
**[correlated subqueries in the HAVING 
clause](https://issues.apache.org/jira/browse/PHOENIX-1388)** and **[using 
subqueries as 
expressions](https://issues.apache.org/jira/browse/PHOENIX-1392)**.
-6. **[DEFAULT 
declaration](https://issues.apache.org/jira/browse/PHOENIX-476)**. When 
creating a table, we should allow a DEFAULT declaration in our CREATE TABLE 
statement.
 7. **[STRUCT type](https://issues.apache.org/jira/browse/PHOENIX-477)**. Allow 
declarations of multiple fields of different data types that would be packed 
into a single cell to reduce the per column storage overhead.
 17. **[OLAP Extensions](https://issues.apache.org/jira/browse/PHOENIX-154)**. 
Support the `WINDOW`, `PARTITION OVER`, `RANK`, and other SQL-92 extensions.
 16. **[Multi-version Row 
Queries](https://issues.apache.org/jira/browse/PHOENIX-590)**. Expose the time 
dimension of rows through a built-in function to allow aggregation and trending 
over multiple row versions.


Reply via email to