Author: jamestaylor
Date: Thu Jul 30 06:02:09 2015
New Revision: 1693388

URL: http://svn.apache.org/r1693388
Log:
Update limitations on VIEW

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

Modified: phoenix/site/publish/views.html
URL: 
http://svn.apache.org/viewvc/phoenix/site/publish/views.html?rev=1693388&r1=1693387&r2=1693388&view=diff
==============================================================================
--- phoenix/site/publish/views.html (original)
+++ phoenix/site/publish/views.html Thu Jul 30 06:02:09 2015
@@ -191,13 +191,12 @@ VALUES('John Doe', CURRENT_DATE(), NEXT
  <h2 id="Limitations">Limitations</h2> 
  <p>Views have the following restrictions:</p> 
  <ol style="list-style-type: decimal"> 
-  <li>An INDEX over a VIEW is only maintained if the updates are made through 
the VIEW. Updates made through the underlying TABLE will not be reflected in 
the index (<a class="externalLink" 
href="https://issues.apache.org/jira/browse/PHOENIX-1499";>PHOENIX-1499</a>).</li>
 
-  <li>The schema of a table may not be changed once it has VIEWs (<a 
class="externalLink" 
href="https://issues.apache.org/jira/browse/PHOENIX-1504";>PHOENIX-1504</a>).</li>
 
-  <li>The primary key constraint of the base TABLE may not be changed by a 
VIEW. In the future, adding to the primary key constraint may be possible (<a 
class="externalLink" 
href="https://issues.apache.org/jira/browse/PHOENIX-978";>PHOENIX-978</a>).</li> 
+  <li>An INDEX over a VIEW is only maintained if the updates are made through 
the VIEW. Updates made through the underlying TABLE or the parent VIEW will not 
be reflected in the index (<a class="externalLink" 
href="https://issues.apache.org/jira/browse/PHOENIX-1499";>PHOENIX-1499</a>).</li>
 
+  <li>A column of a table may not be dropped once it has VIEWs (<a 
class="externalLink" 
href="https://issues.apache.org/jira/browse/PHOENIX-2156";>PHOENIX-2156</a>).</li>
 
+  <li>A primary key column may not be added to a VIEW when its base table has 
a primary key constraint that ends with a variable length column (<a 
class="externalLink" 
href="https://issues.apache.org/jira/browse/PHOENIX-2157";>PHOENIX-2157</a>).</li>
 
   <li>A VIEW may be defined over only a single table through a simple SELECT * 
query. You may not create a VIEW over multiple, joined tables nor over 
aggregations (<a class="externalLink" 
href="https://issues.apache.org/jira/browse/PHOENIX-1505";>PHOENIX-1505</a>, <a 
class="externalLink" 
href="https://issues.apache.org/jira/browse/PHOENIX-1506";>PHOENIX-1506</a>).</li>
 
   <li>If a VIEW is derived from another VIEW, the indexes from the 
base/derived VIEW will not be considered when executing queries (<a 
class="externalLink" 
href="https://issues.apache.org/jira/browse/PHOENIX-1367";>PHOENIX-1367</a>).</li>
 
-  <li>All columns must be projected into a VIEW (i.e. only CREATE VIEW … AS 
SELECT * is supported). Note, however, you may drop non primary key columns 
inherited from the base table in a VIEW after it is created through the ALTER 
VIEW command. Providing a subset of columns and or expressions in the SELECT 
clause will be supported in a future release (<a class="externalLink" 
href="https://issues.apache.org/jira/browse/PHOENIX-1507";>PHOENIX-1507</a>).</li>
 
-  <li>A TABLE that has a VIEW may not be dropped, but instead all VIEWs must 
be dropped first. As of the 3.2/4.2 release, <a class="externalLink" 
href="http://phoenix.apache.org/language/index.html#drop_table";>DROP TABLE</a> 
and <a class="externalLink" 
href="http://phoenix.apache.org/language/index.html#drop_view";>DROP VIEW</a> 
supports a CASCADE option which will cause all tenant-specific views to be 
dropped as well.</li> 
+  <li>All columns must be projected into a VIEW when it’s created (i.e. only 
CREATE VIEW … AS SELECT * is supported). Note, however, you may drop non 
primary key columns inherited from the base table in a VIEW after it is created 
through the ALTER VIEW command. Providing a subset of columns and or 
expressions in the SELECT clause will be supported in a future release (<a 
class="externalLink" 
href="https://issues.apache.org/jira/browse/PHOENIX-1507";>PHOENIX-1507</a>).</li>
 
  </ol> 
 </div>
                        </div>

Modified: phoenix/site/source/src/site/markdown/views.md
URL: 
http://svn.apache.org/viewvc/phoenix/site/source/src/site/markdown/views.md?rev=1693388&r1=1693387&r2=1693388&view=diff
==============================================================================
--- phoenix/site/source/src/site/markdown/views.md (original)
+++ phoenix/site/source/src/site/markdown/views.md Thu Jul 30 06:02:09 2015
@@ -46,11 +46,10 @@ In addition, you may create an INDEX ove
 ## Limitations
 Views have the following restrictions:
 
-1. An INDEX over a VIEW is only maintained if the updates are made through the 
VIEW. Updates made through the underlying TABLE will not be reflected in the 
index ([PHOENIX-1499](https://issues.apache.org/jira/browse/PHOENIX-1499)).
-2. The schema of a table may not be changed once it has VIEWs 
([PHOENIX-1504](https://issues.apache.org/jira/browse/PHOENIX-1504)).
-3. The primary key constraint of the base TABLE may not be changed by a VIEW. 
In the future, adding to the primary key constraint may be possible 
([PHOENIX-978](https://issues.apache.org/jira/browse/PHOENIX-978)).
+1. An INDEX over a VIEW is only maintained if the updates are made through the 
VIEW. Updates made through the underlying TABLE or the parent VIEW will not be 
reflected in the index 
([PHOENIX-1499](https://issues.apache.org/jira/browse/PHOENIX-1499)).
+2. A column of a table may not be dropped once it has VIEWs 
([PHOENIX-2156](https://issues.apache.org/jira/browse/PHOENIX-2156)).
+3. A primary key column may not be added to a VIEW when its base table has a 
primary key constraint that ends with a variable length column 
([PHOENIX-2157](https://issues.apache.org/jira/browse/PHOENIX-2157)).
 4. A VIEW may be defined over only a single table through a simple SELECT * 
query. You may not create a VIEW over multiple, joined tables nor over 
aggregations 
([PHOENIX-1505](https://issues.apache.org/jira/browse/PHOENIX-1505), 
[PHOENIX-1506](https://issues.apache.org/jira/browse/PHOENIX-1506)). 
 5. If a VIEW is derived from another VIEW, the indexes from the base/derived 
VIEW will not be considered when executing queries 
([PHOENIX-1367](https://issues.apache.org/jira/browse/PHOENIX-1367)).
-6. All columns must be projected into a VIEW (i.e. only CREATE VIEW ... AS 
SELECT * is supported). Note, however, you may drop non primary key columns 
inherited from the base table in a VIEW after it is created through the ALTER 
VIEW command. Providing a subset of columns and or expressions in the SELECT 
clause will be supported in a future release 
([PHOENIX-1507](https://issues.apache.org/jira/browse/PHOENIX-1507)).
-7. A TABLE that has a VIEW may not be dropped, but instead all VIEWs must be 
dropped first. As of the 3.2/4.2 release, [DROP 
TABLE](http://phoenix.apache.org/language/index.html#drop_table) and [DROP 
VIEW](http://phoenix.apache.org/language/index.html#drop_view) supports a 
CASCADE option which will cause all tenant-specific views to be dropped as well.
+6. All columns must be projected into a VIEW when it's created (i.e. only 
CREATE VIEW ... AS SELECT * is supported). Note, however, you may drop non 
primary key columns inherited from the base table in a VIEW after it is created 
through the ALTER VIEW command. Providing a subset of columns and or 
expressions in the SELECT clause will be supported in a future release 
([PHOENIX-1507](https://issues.apache.org/jira/browse/PHOENIX-1507)).
 


Reply via email to