Author: stoty
Date: Thu Sep  9 05:55:04 2021
New Revision: 1893163

URL: http://svn.apache.org/viewvc?rev=1893163&view=rev
Log:
PHOENIX-6535 Update obsolete information on website
also replace absolute links with relative ones in wiki links

Modified:
    phoenix/site/publish/Phoenix-in-15-minutes-or-less.html
    phoenix/site/publish/building.html
    phoenix/site/publish/contributing.html
    phoenix/site/publish/develop.html
    phoenix/site/publish/faq.html
    phoenix/site/publish/index.html
    phoenix/site/publish/installation.html
    phoenix/site/publish/issues.html
    phoenix/site/publish/language/datatypes.html
    phoenix/site/publish/language/functions.html
    phoenix/site/publish/language/index.html
    phoenix/site/publish/multi-tenancy.html
    phoenix/site/publish/namspace_mapping.html
    phoenix/site/publish/news.html
    phoenix/site/publish/performance.html
    phoenix/site/publish/phoenix_spark.html
    phoenix/site/publish/python.html
    phoenix/site/publish/recent.html
    phoenix/site/publish/release.html
    phoenix/site/publish/release_notes.html
    phoenix/site/publish/resources.html
    phoenix/site/publish/roadmap.html
    phoenix/site/publish/secondary_indexing.html
    phoenix/site/publish/sequences.html
    phoenix/site/publish/server.html
    phoenix/site/publish/tuning_guide.html
    phoenix/site/source/src/site/markdown/Phoenix-in-15-minutes-or-less.md
    phoenix/site/source/src/site/markdown/building.md
    phoenix/site/source/src/site/markdown/contributing.md
    phoenix/site/source/src/site/markdown/develop.md
    phoenix/site/source/src/site/markdown/faq.md
    phoenix/site/source/src/site/markdown/index.md
    phoenix/site/source/src/site/markdown/installation.md
    phoenix/site/source/src/site/markdown/issues.md
    phoenix/site/source/src/site/markdown/multi-tenancy.md
    phoenix/site/source/src/site/markdown/namspace_mapping.md
    phoenix/site/source/src/site/markdown/news.md
    phoenix/site/source/src/site/markdown/performance.md
    phoenix/site/source/src/site/markdown/phoenix_spark.md
    phoenix/site/source/src/site/markdown/python.md
    phoenix/site/source/src/site/markdown/recent.md
    phoenix/site/source/src/site/markdown/release.md
    phoenix/site/source/src/site/markdown/release_notes.md
    phoenix/site/source/src/site/markdown/resources.md
    phoenix/site/source/src/site/markdown/roadmap.md
    phoenix/site/source/src/site/markdown/secondary_indexing.md
    phoenix/site/source/src/site/markdown/sequences.md
    phoenix/site/source/src/site/markdown/server.md
    phoenix/site/source/src/site/markdown/tuning_guide.md

Modified: phoenix/site/publish/Phoenix-in-15-minutes-or-less.html
URL: 
http://svn.apache.org/viewvc/phoenix/site/publish/Phoenix-in-15-minutes-or-less.html?rev=1893163&r1=1893162&r2=1893163&view=diff
==============================================================================
--- phoenix/site/publish/Phoenix-in-15-minutes-or-less.html (original)
+++ phoenix/site/publish/Phoenix-in-15-minutes-or-less.html Thu Sep  9 05:55:04 
2021
@@ -1,7 +1,7 @@
 
 <!DOCTYPE html>
 <!--
- Generated by Apache Maven Doxia at 2021-08-27
+ Generated by Apache Maven Doxia at 2021-09-08
  Rendered using Reflow Maven Skin 1.1.0 
(http://andriusvelykis.github.io/reflow-maven-skin)
 -->
 <html  xml:lang="en" lang="en">
@@ -178,9 +178,6 @@
  <li>bringing the computation to the data by</li> 
  <li>pushing the predicates in your where clause to a server-side filter</li> 
  <li>executing aggregate queries through server-side hooks (called 
co-processors)</li> 
-</ul> 
-<p>In addition to these items, we’ve got some interesting enhancements in 
the works to further optimize performance:</p> 
-<ul> 
  <li>secondary indexes to improve performance for queries on non row key 
columns</li> 
  <li>stats gathering to improve parallelization and guide choices between 
optimizations</li> 
  <li>skip scan filter to optimize IN, LIKE, and OR queries</li> 
@@ -195,13 +192,13 @@
 <p><i><b>But how can SQL support my favorite HBase technique of 
x,y,z</b></i><br /> Didn’t make it to the last HBase Meetup did you? SQL is 
just a way of expressing <i><b>what you want to get</b></i> not <i><b>how you 
want to get it</b></i>. Check out my <a class="externalLink" 
href="http://files.meetup.com/1350427/IntelPhoenixHBaseMeetup.ppt";>presentation</a>
 for various existing and to-be-done Phoenix features to support your favorite 
HBase trick. Have ideas of your own? We’d love to hear about them: file an <a 
href="issues.html">issue</a> for us and/or join our <a 
href="mailing_list.html">mailing list</a>.</p> 
 <p><i><b>Blah, blah, blah - I just want to get started!</b></i><br /> Ok, 
great! Just follow our <a href="installation.html">install 
instructions</a>:</p> 
 <ul> 
- <li><a href="download.html">download</a> and expand our installation tar</li> 
- <li>copy the phoenix server jar that is compatible with your HBase 
installation into the lib directory of every region server</li> 
- <li>restart the region servers</li> 
- <li>add the phoenix client jar to the classpath of your HBase client</li> 
- <li>download and <a href="installation.html#SQL_Client">setup SQuirrel</a> as 
your SQL client so you can issue adhoc SQL against your HBase cluster</li> 
+ <li><a href="download.html">download</a> and expand our installation binary 
tar corresponding to your HBase version</li> 
+ <li>copy the phoenix server jar into the lib directory of every region server 
and master</li> 
+ <li>restart HBase</li> 
+ <li>add the phoenix client jar to the classpath of your JDBC client or 
application</li> 
+ <li>We have detailed instructions for <a 
href="installation.html#SQL_Client">setting up SQuirreL SQL</a> as your SQL 
client</li> 
 </ul> 
-<p><i><b>I don’t want to download and setup anything else!</b></i><br /> Ok, 
fair enough - you can create your own SQL scripts and execute them using our 
command line tool instead. Let’s walk through an example now. Begin by 
navigating to the <tt>bin/</tt> directory of your Phoenix install location.</p> 
+<p><i><b>I don’t want to download and setup anything else!</b></i><br /> Ok, 
fair enough - you can create your own SQL scripts and execute them using our 
command line tools instead. Let’s walk through an example now. Begin by 
navigating to the <tt>bin/</tt> directory of your Phoenix install location.</p> 
 <ul> 
  <li>First, let’s create a <tt>us_population.sql</tt> file, containing a 
table definition:</li> 
 </ul> 
@@ -230,20 +227,25 @@ CA,San Jose,912332
 </pre>
 </div> 
 <ul> 
- <li>And finally, let’s create a <tt>us_population_queries.sql</tt> file 
containing a query we’d like to run on that data.</li> 
+ <li>Execute the following command from a command terminal to create and 
populate the table</li> 
 </ul> 
 <div class="source"> 
- <pre>SELECT state as &quot;State&quot;,count(city) as &quot;City 
Count&quot;,sum(population) as &quot;Population Sum&quot;
-FROM us_population
-GROUP BY state
-ORDER BY sum(population) DESC;
+ <pre>./psql.py &lt;your_zookeeper_quorum&gt; us_population.sql 
us_population.csv
 </pre>
 </div> 
 <ul> 
- <li>Execute the following command from a command terminal</li> 
+ <li>Start the interactive sql client</li> 
 </ul> 
 <div class="source"> 
- <pre>./psql.py &lt;your_zookeeper_quorum&gt; us_population.sql 
us_population.csv us_population_queries.sql
+ <pre>./sqlline.py &lt;your_zookeeper_quorum&gt;
+</pre>
+</div> 
+<p>and issue a query </p> 
+<div class="source"> 
+ <pre>SELECT state as &quot;State&quot;,count(city) as &quot;City 
Count&quot;,sum(population) as &quot;Population Sum&quot;
+FROM us_population
+GROUP BY state
+ORDER BY sum(population) DESC;
 </pre>
 </div> 
 <p>Congratulations! You’ve just created your first Phoenix table, inserted 
data into it, and executed an aggregate query with just a few lines of code in 
15 minutes or less! </p> 

Modified: phoenix/site/publish/building.html
URL: 
http://svn.apache.org/viewvc/phoenix/site/publish/building.html?rev=1893163&r1=1893162&r2=1893163&view=diff
==============================================================================
--- phoenix/site/publish/building.html (original)
+++ phoenix/site/publish/building.html Thu Sep  9 05:55:04 2021
@@ -1,14 +1,14 @@
 
 <!DOCTYPE html>
 <!--
- Generated by Apache Maven Doxia at 2021-08-27
+ Generated by Apache Maven Doxia at 2021-09-08
  Rendered using Reflow Maven Skin 1.1.0 
(http://andriusvelykis.github.io/reflow-maven-skin)
 -->
 <html  xml:lang="en" lang="en">
 
        <head>
                <meta charset="UTF-8" />
-               <title>Building Phoenix Project | Apache Phoenix</title>
+               <title>Building the Main Phoenix Project | Apache 
Phoenix</title>
                <meta name="viewport" content="width=device-width, 
initial-scale=1.0" />
                <meta name="description" content="" />
                <meta http-equiv="content-language" content="en" />
@@ -167,65 +167,31 @@
                <div class="span12">
                        <div class="body-content">
 <div class="page-header">
- <h1>Building Phoenix Project</h1>
+ <h1>Building the Main Phoenix Project</h1>
 </div> 
-<p>Phoenix is a fully mavenized project. Download <a 
href="source.html">source</a> and build simply by doing:</p> 
+<p>Phoenix consists of several subprojects.</p> 
+<p>The core of the project is the <tt>phoenix</tt> project, which depends on 
the <tt>phoenix-thirdparty</tt>, <tt>phoenix-omid</tt> and 
<tt>phoenix-tephra</tt> projects.</p> 
+<p><tt>phoenix-queryserver</tt> and <tt>phoenix-connectors</tt> are optional 
packages that depend on the <tt>phoenix</tt> project.</p> 
+<p>Check out the <a href="source.html">source</a> and follow the build 
instructions in BUILDING.md (or README.md) in the root directory.</p> 
+<h1>Using Phoenix in a Maven Project</h1> 
+<p>Phoenix is also hosted at Apache Maven Repository and Maven Central. You 
can add it to your mavenized project by adding the following to your pom:</p> 
 <div class="source"> 
- <pre>$ mvn package
-</pre> 
-</div> 
-<p>builds, runs fast unit tests and package Phoenix and put the resulting jars 
(phoenix-[version].jar and phoenix-[version]-client.jar) in the generated 
phoenix-core/target/ and phoenix-assembly/target/ directories respectively.</p> 
-<p>To build, but skip running the fast unit tests, you can do:</p> 
-<div class="source"> 
- <pre> $ mvn package -DskipTests
-</pre> 
-</div> 
-<p>To build against hadoop2, you can do:</p> 
-<div class="source"> 
- <pre> $ mvn package -DskipTests -Dhadoop.profile=2
-</pre> 
-</div> 
-<p>To run all tests including long running integration tests</p> 
-<div class="source"> 
- <pre> $ mvn install
-</pre> 
-</div> 
-<p>To only build the generated parser (i.e. <tt>PhoenixSQLLexer</tt> and 
<tt>PhoenixSQLParser</tt>), you can do:</p> 
-<div class="source"> 
- <pre> $ mvn install -DskipTests
- $ mvn process-sources
-</pre> 
-</div> 
-<p>To build an Eclipse project, install the m2e plugin and do an 
File-&gt;Import…-&gt;Import Existing Maven Projects selecting the root 
directory of Phoenix.</p> 
-<div class="section"> 
- <h2 id="Maven">Maven</h2> 
- <p>Phoenix is also hosted at Apache Maven Repository. You can add it to your 
mavenized project by adding the following to your pom:</p> 
- <div class="source"> 
-  <pre> &lt;repositories&gt;
-   ...
-    &lt;repository&gt;
-      &lt;id&gt;apache release&lt;/id&gt;
-      
&lt;url&gt;https://repository.apache.org/content/repositories/releases/&lt;/url&gt;
-    &lt;/repository&gt;
-    ...
-  &lt;/repositories&gt;
-  
-  &lt;dependencies&gt;
+ <pre>  &lt;dependencies&gt;
     ...
     &lt;dependency&gt;
         &lt;groupId&gt;org.apache.phoenix&lt;/groupId&gt;
-        &lt;artifactId&gt;phoenix-core&lt;/artifactId&gt;
-        &lt;version&gt;[version]&lt;/version&gt;
+        
&lt;artifactId&gt;phoenix-client-hbase-[hbase.profile]&lt;/artifactId&gt;
+        &lt;version&gt;[phoenix.version]&lt;/version&gt;
     &lt;/dependency&gt;
     ...
   &lt;/dependencies&gt;
 </pre> 
- </div> 
- <p>Note: [version] can be replaced by 3.1.0, 4.1.0, 3.0.0-incubating, 
4.0.0-incubating, etc.</p> 
 </div> 
+<p>Where [phoenix.version] is the phoenix release i.e 5.1.2 or 4.16.1, and 
[hbase.profile] is the supported HBase version, which you can see listed on the 
<a href="download.html">download</a> page.</p> 
 <div class="section"> 
  <h2 id="Branches">Branches</h2> 
- <p>Phoenix 3.0 is running against hbase0.94+, Phoenix 4.0 is running against 
hbase0.98.1+ and Phoenix master branch is running against hbase trunk 
branch.</p> 
+ <p>The main Phoenix project currently has two active branches.</p> 
+ <p>The 4.x branch works with HBase 1 and Hadoop 2, while the 5.x branch works 
with HBase 2 and Hadoop 3. See the <a href="download.html">download</a> page 
and BUILDING.md for the HBase versions supported by each release.</p> 
  <hr /> 
  <p>See also: </p> 
  <p><a href="building_website.html">Building Project Web Site</a></p> 

Modified: phoenix/site/publish/contributing.html
URL: 
http://svn.apache.org/viewvc/phoenix/site/publish/contributing.html?rev=1893163&r1=1893162&r2=1893163&view=diff
==============================================================================
--- phoenix/site/publish/contributing.html (original)
+++ phoenix/site/publish/contributing.html Thu Sep  9 05:55:04 2021
@@ -1,7 +1,7 @@
 
 <!DOCTYPE html>
 <!--
- Generated by Apache Maven Doxia at 2021-08-27
+ Generated by Apache Maven Doxia at 2021-09-08
  Rendered using Reflow Maven Skin 1.1.0 
(http://andriusvelykis.github.io/reflow-maven-skin)
 -->
 <html  xml:lang="en" lang="en">
@@ -180,6 +180,7 @@
   <li>Submit the patch</li> 
  </ol> 
  <p>These steps are explained in greater detail below.</p> 
+ <p>Note that the instructions below are for the main Phoenix project. Use the 
corresponding <a href="source.html">repository</a> for the other subprojects. 
Tephra and Omid also have their own <a href="issues.html">JIRA project</a></p> 
  <div class="section"> 
   <h3 id="Discuss_on_the_mailing_list">Discuss on the mailing list</h3> 
   <p>It’s often best to discuss a change on the public mailing lists before 
creating and submitting a patch.</p> 

Modified: phoenix/site/publish/develop.html
URL: 
http://svn.apache.org/viewvc/phoenix/site/publish/develop.html?rev=1893163&r1=1893162&r2=1893163&view=diff
==============================================================================
--- phoenix/site/publish/develop.html (original)
+++ phoenix/site/publish/develop.html Thu Sep  9 05:55:04 2021
@@ -1,7 +1,7 @@
 
 <!DOCTYPE html>
 <!--
- Generated by Apache Maven Doxia at 2021-08-27
+ Generated by Apache Maven Doxia at 2021-09-08
  Rendered using Reflow Maven Skin 1.1.0 
(http://andriusvelykis.github.io/reflow-maven-skin)
 -->
 <html  xml:lang="en" lang="en">
@@ -172,6 +172,7 @@
 <p>Below are the steps necessary to setup your development environment so that 
you may contribute to Apache Phoenix.</p> 
 <ul> 
  <li><a href="#gettingStarted">Getting Started</a></li> 
+ <li><a href="#otherProjects">Other Phoenix subprojects</a></li> 
  <li><a href="#localGit">Setup local Git Repository</a></li> 
  <li><a href="#eclipse">Eclipse</a> 
   <ul> 
@@ -216,6 +217,12 @@ export PATH=$M2_HOME/bin:$PATH
 </pre> 
    </div></li> 
  </ol> 
+ <p><a name="otherProjects" id="otherProjects"></a></p> 
+</div> 
+<div class="section"> 
+ <h2 id="Other_Phoenix_Subprojects">Other Phoenix Subprojects</h2> 
+ <p>The instructions here are for the main Phoenix project. For the other 
subprojects, use the corresponding <a href="source.html">repository</a> and <a 
href="issues.html">JIRA project</a>.</p> 
+ <p>The Eclipse and IntelliJ setup instructions may not necessarily work well 
for the other projects.</p> 
  <p><a name="localGit" id="localGit"></a></p> 
 </div> 
 <div class="section"> 

Modified: phoenix/site/publish/faq.html
URL: 
http://svn.apache.org/viewvc/phoenix/site/publish/faq.html?rev=1893163&r1=1893162&r2=1893163&view=diff
==============================================================================
--- phoenix/site/publish/faq.html (original)
+++ phoenix/site/publish/faq.html Thu Sep  9 05:55:04 2021
@@ -1,7 +1,7 @@
 
 <!DOCTYPE html>
 <!--
- Generated by Apache Maven Doxia at 2021-08-27
+ Generated by Apache Maven Doxia at 2021-09-08
  Rendered using Reflow Maven Skin 1.1.0 
(http://andriusvelykis.github.io/reflow-maven-skin)
 -->
 <html  xml:lang="en" lang="en">
@@ -188,10 +188,10 @@
 <div class="section"> 
  <div class="section"> 
   <h3 id="I_want_to_get_started._Is_there_a_Phoenix_Hello_World">I want to get 
started. Is there a Phoenix <i>Hello World</i>?</h3> 
-  <p><i>Pre-requisite:</i> Download latest Phoenix from <a 
href="download.html">here</a> and copy phoenix-*.jar to HBase lib folder and 
restart HBase.</p> 
+  <p><i>Pre-requisite:</i> <a href="download.html">Download</a> and <a 
href="installation.html">install</a> the latest Phoenix.</p> 
   <p><b>1. Using console</b></p> 
   <ol style="list-style-type: decimal"> 
-   <li>Start Sqlline: <tt>$ sqlline.py [zookeeper]</tt></li> 
+   <li>Start Sqlline: <tt>$ sqlline.py [zookeeper quorum hosts]</tt></li> 
    <li>Execute the following statements when Sqlline connects:</li> 
   </ol> 
   <div class="source"> 
@@ -229,7 +229,7 @@ public class test {
                Statement stmt = null;
                ResultSet rset = null;
                
-               Connection con = 
DriverManager.getConnection(&quot;jdbc:phoenix:[zookeeper]&quot;);
+               Connection con = 
DriverManager.getConnection(&quot;jdbc:phoenix:[zookeeper quorum hosts]&quot;);
                stmt = con.createStatement();
                
                stmt.executeUpdate(&quot;create table test (mykey integer not 
null primary key, mycolumn varchar)&quot;);
@@ -259,7 +259,7 @@ public class test {
   <div class="section"> 
    <h4 id="Thick_Driver">Thick Driver</h4> 
    <p>The Phoenix (Thick) Driver JDBC URL syntax is as follows (where elements 
in square brackets are optional):</p> 
-   <p><tt>jdbc:phoenix:[comma-separated ZooKeeper Quorum [:port [:hbase root 
znode [:kerberos_principal [:path to kerberos keytab] ] ] ]</tt></p> 
+   <p><tt>jdbc:phoenix:[comma-separated ZooKeeper Quorum Hosts [: ZK port 
[:hbase root znode [:kerberos_principal [:path to kerberos keytab] ] ] 
]</tt></p> 
    <p>The simplest URL is:</p> 
    <p><tt>jdbc:phoenix:localhost</tt></p> 
    <p>Whereas the most complicated URL is:</p> 
@@ -315,7 +315,7 @@ public class test {
   <p><tt>CREATE TABLE TEST (HOST VARCHAR NOT NULL PRIMARY KEY, DESCRIPTION 
VARCHAR) SALT_BUCKETS=16</tt></p> 
   <p>Note: Ideally for a 16 region server cluster with quad-core CPUs, choose 
salt buckets between 32-64 for optimal performance.</p> 
   <ul> 
-   <li><b>Per-split</b> table Salting does automatic table splitting but in 
case you want to exactly control where table split occurs with out adding extra 
byte or change row key order then you can pre-split a table.</li> 
+   <li><b>Pre-split</b> table Salting does automatic table splitting but in 
case you want to exactly control where table split occurs with out adding extra 
byte or change row key order then you can pre-split a table.</li> 
   </ul> 
   <p>Example: </p> 
   <p><tt>CREATE TABLE TEST (HOST VARCHAR NOT NULL PRIMARY KEY, DESCRIPTION 
VARCHAR) SPLIT ON ('CS','EU','NA')</tt></p> 
@@ -355,6 +355,7 @@ public class test {
   </ul> 
   <p><tt>create index idx on test (col1) include (col2)</tt></p> 
   <p>Upsert rows in this test table and Phoenix query optimizer will choose 
correct index to use. You can see in <a 
href="language/index.html#explain">explain plan</a> if Phoenix is using the 
index table. You can also give a <a href="language/index.html#hint">hint</a> in 
Phoenix query to use a specific index.</p> 
+  <p>See <a href="secondary_indexing.html">Secondary Indexing</a> for further 
information</p> 
  </div> 
  <div class="section"> 
   <h3 id="Why_isnt_my_secondary_index_being_used">Why isn’t my secondary 
index being used?</h3> 
@@ -362,6 +363,7 @@ public class test {
   <p>Example: DDL <tt>create table usertable (id varchar primary key, 
firstname varchar, lastname varchar); create index idx_name on usertable 
(firstname);</tt></p> 
   <p>Query: DDL <tt>select id, firstname, lastname from usertable where 
firstname = 'foo';</tt></p> 
   <p>Index would not be used in this case as lastname is not part of indexed 
or covered column. This can be verified by looking at the explain plan. To fix 
this create index that has either lastname part of index or covered column. 
Example: <tt>create idx_name on usertable (firstname) include 
(lastname);</tt></p> 
+  <p>You can force Phoenix to use secondary for uncovered columns by 
specifying an <a href="index.html#index_hint">index hint</a></p> 
  </div> 
  <div class="section"> 
   <h3 id="How_fast_is_Phoenix_Why_is_it_so_fast">How fast is Phoenix? Why is 
it so fast?</h3> 
@@ -374,11 +376,13 @@ public class test {
  </div> 
  <div class="section"> 
   <h3 id="How_do_I_connect_to_secure_HBase_cluster">How do I connect to secure 
HBase cluster?</h3> 
-  <p>Check out excellent post by Anil Gupta <a class="externalLink" 
href="http://bigdatanoob.blogspot.com/2013/09/connect-phoenix-to-secure-hbase-cluster.html";>http://bigdatanoob.blogspot.com/2013/09/connect-phoenix-to-secure-hbase-cluster.html</a></p>
 
+  <p>Specify the principal and corresponding keytab in the JDBC URL as show 
above. For ancient Phoenix versions heck out the excellent <a 
class="externalLink" 
href="http://bigdatanoob.blogspot.com/2013/09/connect-phoenix-to-secure-hbase-cluster.html";>post</a>
 by Anil Gupta </p> 
  </div> 
  <div class="section"> 
-  <h3 id="How_do_I_connect_with_HBase_running_on_Hadoop-2">How do I connect 
with HBase running on Hadoop-2?</h3> 
-  <p>Hadoop-2 profile exists in Phoenix pom.xml. </p> 
+  <h3 id="What_HBase_and_Hadoop_versions_are_supported_">What HBase and Hadoop 
versions are supported ?</h3> 
+  <p>Phoenix 4.x supports HBase 1.x running on Hadoop 2</p> 
+  <p>Phoenix 5.x supports HBase 2.x running on Hadoop 3</p> 
+  <p>See the release notes and BULDING.md in recent releases for the exact 
versions supported, and on how to build Phoenix for specific HBase and Hadoop 
versions</p> 
  </div> 
  <div class="section"> 
   <h3 
id="Can_phoenix_work_on_tables_with_arbitrary_timestamp_as_flexible_as_HBase_API">Can
 phoenix work on tables with arbitrary timestamp as flexible as HBase API?</h3> 

Modified: phoenix/site/publish/index.html
URL: 
http://svn.apache.org/viewvc/phoenix/site/publish/index.html?rev=1893163&r1=1893162&r2=1893163&view=diff
==============================================================================
--- phoenix/site/publish/index.html (original)
+++ phoenix/site/publish/index.html Thu Sep  9 05:55:04 2021
@@ -1,7 +1,7 @@
 
 <!DOCTYPE html>
 <!--
- Generated by Apache Maven Doxia at 2021-07-05
+ Generated by Apache Maven Doxia at 2021-09-08
  Rendered using Reflow Maven Skin 1.1.0 
(http://andriusvelykis.github.io/reflow-maven-skin)
 -->
 <html  xml:lang="en" lang="en">
@@ -198,7 +198,7 @@
   <li>the flexibility of late-bound, schema-on-read capabilities from the 
NoSQL world by leveraging HBase as its backing store</li> 
  </ul> 
  <p>Apache Phoenix is fully integrated with other Hadoop products such as 
Spark, Hive, Pig, Flume, and Map Reduce.</p> 
- <p> Who is using Apache Phoenix? Read more <a 
href="who_is_using.html">here...</a> </p>
+ <p> Who is using Apache Phoenix? Read more <a 
href="who_is_using.html">here...</a> </p> 
 </div> 
 <div class="section"> 
  <h2 id="Mission">Mission</h2> 
@@ -206,7 +206,7 @@
 </div> 
 <div class="section"> 
  <h2 id="Quick_Start">Quick Start</h2> 
- <p>Tired of reading already and just want to get started? Take a look at our 
<a href="faq.html">FAQs</a>, listen to the Apache Phoenix talk from <a 
class="externalLink" href="https://www.youtube.com/watch?v=XGa0SyJMH94";>Hadoop 
Summit 2015</a>, review the <a class="externalLink" 
href="http://phoenix.apache.org/presentations/OC-HUG-2014-10-4x3.pdf";>overview 
presentation</a>, and jump over to our quick start guide <a 
href="Phoenix-in-15-minutes-or-less.html">here</a>.</p> 
+ <p>Tired of reading already and just want to get started? Take a look at our 
<a href="faq.html">FAQs</a>, listen to the Apache Phoenix talk from <a 
class="externalLink" href="https://www.youtube.com/watch?v=XGa0SyJMH94";>Hadoop 
Summit 2015</a>, review the <a 
href="/presentations/OC-HUG-2014-10-4x3.pdf">overview presentation</a>, and 
jump over to our quick start guide <a 
href="Phoenix-in-15-minutes-or-less.html">here</a>.</p> 
 </div> 
 <div class="section"> 
  <h2 id="SQL_Support">SQL Support</h2> 

Modified: phoenix/site/publish/installation.html
URL: 
http://svn.apache.org/viewvc/phoenix/site/publish/installation.html?rev=1893163&r1=1893162&r2=1893163&view=diff
==============================================================================
--- phoenix/site/publish/installation.html (original)
+++ phoenix/site/publish/installation.html Thu Sep  9 05:55:04 2021
@@ -1,7 +1,7 @@
 
 <!DOCTYPE html>
 <!--
- Generated by Apache Maven Doxia at 2021-08-27
+ Generated by Apache Maven Doxia at 2021-09-08
  Rendered using Reflow Maven Skin 1.1.0 
(http://andriusvelykis.github.io/reflow-maven-skin)
 -->
 <html  xml:lang="en" lang="en">
@@ -172,10 +172,16 @@
  </div> 
  <p>To install a pre-built phoenix, use these directions:</p> 
  <ul> 
-  <li>Download and expand the latest phoenix-[version]-bin.tar.</li> 
-  <li>Add the phoenix-[version]-server.jar to the classpath of all HBase 
region server and master and remove any previous version. An easy way to do 
this is to copy it into the HBase lib directory (use phoenix-core-[version].jar 
for Phoenix 3.x)</li> 
+  <li><a href="download.html">Download</a> and expand the latest 
phoenix-hbase-[hbase.version][phoenix.version]-bin.tar.gz for your HBase 
version.</li> 
+  <li>Add the phoenix-server-hbase-[hbase.version]-[phoenix.version].jar to 
the classpath of all HBase region servers and masters and remove any previous 
version. An easy way to do this is to copy it into the HBase lib directory</li> 
   <li>Restart HBase.</li> 
-  <li>Add the phoenix-[version]-client.jar to the classpath of any Phoenix 
client.</li> 
+  <li>Add the phoenix-client-hbase-[hbase.version]-[phoenix.version].jar to 
the classpath of any JDBC client.</li> 
+ </ul> 
+ <p>To install Phoenix from source:</p> 
+ <ul> 
+  <li><a href="download.html">Download</a> and expand the latest 
phoenix-[phoenix.version]-src.tar.gz for your HBase version, or check it out 
from the main source <a href="source.html">repository</a></li> 
+  <li>Follow the build instructions in BUILDING.md in the root directory of 
the source distribution/repository to build the binary assembly.</li> 
+  <li>Follow the instructions above, but use the assembly built from 
source.</li> 
  </ul> 
  <div class="section"> 
   <h3 id="Getting_Started">Getting Started</h3> 
@@ -184,16 +190,16 @@
    <h4 id="Command_Line">Command Line</h4> 
    <p>A terminal interface to execute SQL from the command line is now bundled 
with Phoenix. To start it, execute the following from the bin directory:</p> 
    <div class="source"> 
-    <pre>$ sqlline.py localhost
+    <pre>$ sqlline.py [zk quorum hosts]
 </pre> 
    </div> 
    <p>To execute SQL scripts from the command line, you can include a SQL file 
argument like this:</p> 
    <div class="source"> 
-    <pre>$ sqlline.py localhost ../examples/stock_symbol.sql
+    <pre>$ sqlline.py [zk quorum hosts] ../examples/stock_symbol.sql
 </pre> 
    </div> 
    <p><img src="images/sqlline.png" alt="sqlline" /></p> 
-   <p>For more information, see the <a class="externalLink" 
href="http://www.hydromatic.net/sqlline/manual.html";>manual</a>.</p> 
+   <p>For more information, see the <a class="externalLink" 
href="https://julianhyde.github.io/sqlline/manual.html";>manual</a>.</p> 
    <div class="section"> 
     <h5 id="Loading_Data">Loading Data</h5> 
     <p>In addition, you can use the bin/psql.py to load CSV data or execute 
SQL scripts. For example:</p> 
@@ -210,7 +216,7 @@
    </div> 
   </div> 
   <div class="section"> 
-   <h4 id="SQL_Client">SQL Client</h4> 
+   <h4 id="SQuirreL_SQL_Client">SQuirreL SQL Client</h4> 
    <p>If you’d rather use a client GUI to interact with Phoenix, download 
and install <a class="externalLink" 
href="http://squirrel-sql.sourceforge.net/";>SQuirrel</a>. Since Phoenix is a 
JDBC driver, integration with tools such as this are seamless. Here are the 
setup steps necessary:</p> 
    <ol style="list-style-type: decimal"> 
     <li>Remove prior phoenix-[<i>oldversion</i>]-client.jar from the lib 
directory of SQuirrel, copy phoenix-[<i>newversion</i>]-client.jar to the lib 
directory (<i>newversion</i> should be compatible with the version of the 
phoenix server jar used with your HBase installation)</li> 
@@ -225,12 +231,12 @@
    </ol> 
    <p>Through SQuirrel, you can issue SQL statements in the SQL tab (create 
tables, insert data, run queries), and inspect table metadata in the Object tab 
(i.e. list tables, their columns, primary keys, and types).</p> 
    <p><img src="images/squirrel.png" alt="squirrel" /></p> 
+   <p>Note that most graphical clients that support generic JDBC drives should 
also work, and the setup process is usually similar.</p> 
   </div> 
  </div> 
  <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> 
-  <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>
                        </div>

Modified: phoenix/site/publish/issues.html
URL: 
http://svn.apache.org/viewvc/phoenix/site/publish/issues.html?rev=1893163&r1=1893162&r2=1893163&view=diff
==============================================================================
--- phoenix/site/publish/issues.html (original)
+++ phoenix/site/publish/issues.html Thu Sep  9 05:55:04 2021
@@ -1,7 +1,7 @@
 
 <!DOCTYPE html>
 <!--
- Generated by Apache Maven Doxia at 2021-08-27
+ Generated by Apache Maven Doxia at 2021-09-08
  Rendered using Reflow Maven Skin 1.1.0 
(http://andriusvelykis.github.io/reflow-maven-skin)
 -->
 <html  xml:lang="en" lang="en">
@@ -172,8 +172,11 @@
 <p>This project uses JIRA issue tracking and project management application. 
Issues, bugs, and feature requests should be submitted to the following:</p> 
 <hr /> 
 <p><a class="externalLink" 
href="https://issues.apache.org/jira/browse/PHOENIX";>https://issues.apache.org/jira/browse/PHOENIX</a></p>
 
+<p><a class="externalLink" 
href="https://issues.apache.org/jira/secure/CreateIssue!default.jspa";>Create 
New Issue</a> | <a class="externalLink" 
href="https://issues.apache.org/jira/browse/PHOENIX/?selectedTab=com.atlassian.jira.jira-projects-plugin:issues-panel";>Existing
 Issues Summary</a> | <a class="externalLink" 
href="https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&amp;mode=hide&amp;jqlQuery=project+%3D+PHOENIX";>All
 Issues</a> | <a class="externalLink" 
href="https://issues.apache.org/jira/browse/PHOENIX?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel";>Road
 Map</a></p> 
 <hr /> 
-<p><a class="externalLink" 
href="https://issues.apache.org/jira/secure/CreateIssue!default.jspa";>Create 
New Issue</a> | <a class="externalLink" 
href="https://issues.apache.org/jira/browse/PHOENIX/?selectedTab=com.atlassian.jira.jira-projects-plugin:issues-panel";>Existing
 Issues Summary</a> | <a class="externalLink" 
href="https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&amp;mode=hide&amp;jqlQuery=project+%3D+PHOENIX";>All
 Issues</a> | <a class="externalLink" 
href="https://issues.apache.org/jira/browse/PHOENIX?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel";>Road
 Map</a></p>
+<p>The Tephra and Omid sub-projects are using separate JIRA projects for 
historical reasons:</p> 
+<p><a class="externalLink" 
href="https://issues.apache.org/jira/browse/TEPHRA";>https://issues.apache.org/jira/browse/TEPHRA</a></p>
 
+<p><a class="externalLink" 
href="https://issues.apache.org/jira/browse/OMID";>https://issues.apache.org/jira/browse/OMID</a></p>
                        </div>
                </div>
        </div>

Modified: phoenix/site/publish/language/datatypes.html
URL: 
http://svn.apache.org/viewvc/phoenix/site/publish/language/datatypes.html?rev=1893163&r1=1893162&r2=1893163&view=diff
==============================================================================
--- phoenix/site/publish/language/datatypes.html (original)
+++ phoenix/site/publish/language/datatypes.html Thu Sep  9 05:55:04 2021
@@ -1,7 +1,7 @@
 
 <!DOCTYPE html>
 <!--
- Generated by Apache Maven Doxia at 2021-08-27
+ Generated by Apache Maven Doxia at 2021-09-08
  Rendered using Reflow Maven Skin 1.1.0 
(http://andriusvelykis.github.io/reflow-maven-skin)
 -->
 <html  xml:lang="en" lang="en">

Modified: phoenix/site/publish/language/functions.html
URL: 
http://svn.apache.org/viewvc/phoenix/site/publish/language/functions.html?rev=1893163&r1=1893162&r2=1893163&view=diff
==============================================================================
--- phoenix/site/publish/language/functions.html (original)
+++ phoenix/site/publish/language/functions.html Thu Sep  9 05:55:04 2021
@@ -1,7 +1,7 @@
 
 <!DOCTYPE html>
 <!--
- Generated by Apache Maven Doxia at 2021-08-27
+ Generated by Apache Maven Doxia at 2021-09-08
  Rendered using Reflow Maven Skin 1.1.0 
(http://andriusvelykis.github.io/reflow-maven-skin)
 -->
 <html  xml:lang="en" lang="en">

Modified: phoenix/site/publish/language/index.html
URL: 
http://svn.apache.org/viewvc/phoenix/site/publish/language/index.html?rev=1893163&r1=1893162&r2=1893163&view=diff
==============================================================================
--- phoenix/site/publish/language/index.html (original)
+++ phoenix/site/publish/language/index.html Thu Sep  9 05:55:04 2021
@@ -1,7 +1,7 @@
 
 <!DOCTYPE html>
 <!--
- Generated by Apache Maven Doxia at 2021-08-27
+ Generated by Apache Maven Doxia at 2021-09-08
  Rendered using Reflow Maven Skin 1.1.0 
(http://andriusvelykis.github.io/reflow-maven-skin)
 -->
 <html  xml:lang="en" lang="en">

Modified: phoenix/site/publish/multi-tenancy.html
URL: 
http://svn.apache.org/viewvc/phoenix/site/publish/multi-tenancy.html?rev=1893163&r1=1893162&r2=1893163&view=diff
==============================================================================
--- phoenix/site/publish/multi-tenancy.html (original)
+++ phoenix/site/publish/multi-tenancy.html Thu Sep  9 05:55:04 2021
@@ -1,7 +1,7 @@
 
 <!DOCTYPE html>
 <!--
- Generated by Apache Maven Doxia at 2021-08-27
+ Generated by Apache Maven Doxia at 2021-09-08
  Rendered using Reflow Maven Skin 1.1.0 
(http://andriusvelykis.github.io/reflow-maven-skin)
 -->
 <html  xml:lang="en" lang="en">
@@ -215,7 +215,7 @@ SELECT * FROM base.event
 WHERE event_type='L';
 </pre> 
   </div> 
-  <p>The tenant_id column is neither visible nor accessible to a 
tenant-specific view. Any reference to it will cause a ColumnNotFoundException. 
Just like any other Phoenix view, whether or not this view is updatable is 
based on the rules explained <a href="views.html#Updatable_Views">here</a>. In 
addition, indexes may be added to tenant-specific views just like to regular 
tables and views (with <a class="externalLink" 
href="http://phoenix.apache.org/views.html#Limitations";>these</a> 
limitations).</p> 
+  <p>The tenant_id column is neither visible nor accessible to a 
tenant-specific view. Any reference to it will cause a ColumnNotFoundException. 
Just like any other Phoenix view, whether or not this view is updatable is 
based on the rules explained <a href="views.html#Updatable_Views">here</a>. In 
addition, indexes may be added to tenant-specific views just like to regular 
tables and views (with <a href="views.html#Limitations">these</a> 
limitations).</p> 
  </div> 
  <div class="section"> 
   <h3 id="Tenant_Data_Isolation">Tenant Data Isolation</h3> 

Modified: phoenix/site/publish/namspace_mapping.html
URL: 
http://svn.apache.org/viewvc/phoenix/site/publish/namspace_mapping.html?rev=1893163&r1=1893162&r2=1893163&view=diff
==============================================================================
--- phoenix/site/publish/namspace_mapping.html (original)
+++ phoenix/site/publish/namspace_mapping.html Thu Sep  9 05:55:04 2021
@@ -1,7 +1,7 @@
 
 <!DOCTYPE html>
 <!--
- Generated by Apache Maven Doxia at 2021-08-27
+ Generated by Apache Maven Doxia at 2021-09-08
  Rendered using Reflow Maven Skin 1.1.0 
(http://andriusvelykis.github.io/reflow-maven-skin)
 -->
 <html  xml:lang="en" lang="en">
@@ -198,9 +198,9 @@
  <h2 id="Grammer_Available">Grammer Available</h2> 
  <p>Following DDL statements can be used to interact with schema.</p> 
  <ul> 
-  <li> <p><a class="externalLink" 
href="https://phoenix.apache.org/language/index.html#create_schema";>CREATE 
SCHEMA</a></p></li> 
-  <li> <p><a class="externalLink" 
href="https://phoenix.apache.org/language/index.html#use";>USE 
SCHEMA</a></p></li> 
-  <li> <p><a class="externalLink" 
href="https://phoenix.apache.org/language/index.html#drop_schema";>DROP 
SCHEMA</a> </p></li> 
+  <li> <p><a href="language/index.html#create_schema">CREATE 
SCHEMA</a></p></li> 
+  <li> <p><a href="language/index.html#use">USE SCHEMA</a></p></li> 
+  <li> <p><a href="language/index.html#drop_schema">DROP SCHEMA</a> </p></li> 
  </ul> 
 </div> 
 <div class="section"> 

Modified: phoenix/site/publish/news.html
URL: 
http://svn.apache.org/viewvc/phoenix/site/publish/news.html?rev=1893163&r1=1893162&r2=1893163&view=diff
==============================================================================
--- phoenix/site/publish/news.html (original)
+++ phoenix/site/publish/news.html Thu Sep  9 05:55:04 2021
@@ -1,7 +1,7 @@
 
 <!DOCTYPE html>
 <!--
- Generated by Apache Maven Doxia at 2021-08-27
+ Generated by Apache Maven Doxia at 2021-09-08
  Rendered using Reflow Maven Skin 1.1.0 
(http://andriusvelykis.github.io/reflow-maven-skin)
 -->
 <html  xml:lang="en" lang="en">
@@ -175,27 +175,27 @@
 <div class="section"> 
  <div class="section"> 
   <div class="section"> 
-   <h4 id="Phoenix_5.1.2_released_June_7_2021"><a class="externalLink" 
href="https://phoenix.apache.org/download.html";>Phoenix 5.1.2 released</a> 
(June 7, 2021)</h4> 
+   <h4 id="Phoenix_5.1.2_released_June_7_2021"><a href="download.html">Phoenix 
5.1.2 released</a> (June 7, 2021)</h4> 
    <hr /> 
   </div> 
   <div class="section"> 
-   <h4 id="Phoenix_4.16.1_released_May_21_2021"><a class="externalLink" 
href="https://phoenix.apache.org/download.html";>Phoenix 4.16.1 released</a> 
(May 21, 2021)</h4> 
+   <h4 id="Phoenix_4.16.1_released_May_21_2021"><a 
href="download.html">Phoenix 4.16.1 released</a> (May 21, 2021)</h4> 
    <hr /> 
   </div> 
   <div class="section"> 
-   <h4 id="Monthly_Tech_Talks_started_March_4_2021"><a class="externalLink" 
href="https://phoenix.apache.org/tech_talks.html";>Monthly Tech Talks 
started</a> (March 4, 2021)</h4> 
+   <h4 id="Monthly_Tech_Talks_started_March_4_2021"><a 
href="tech_talks.html">Monthly Tech Talks started</a> (March 4, 2021)</h4> 
    <hr /> 
   </div> 
   <div class="section"> 
-   <h4 id="Phoenix_5.1.1_released_March_1_2021"><a class="externalLink" 
href="https://phoenix.apache.org/download.html";>Phoenix 5.1.1 released</a> 
(March 1, 2021)</h4> 
+   <h4 id="Phoenix_5.1.1_released_March_1_2021"><a 
href="download.html">Phoenix 5.1.1 released</a> (March 1, 2021)</h4> 
    <hr /> 
   </div> 
   <div class="section"> 
-   <h4 id="Phoenix_4.16.0_released_February_23_2020"><a class="externalLink" 
href="https://phoenix.apache.org/download.html";>Phoenix 4.16.0 released</a> 
(February 23, 2020)</h4> 
+   <h4 id="Phoenix_4.16.0_released_February_23_2020"><a 
href="download.html">Phoenix 4.16.0 released</a> (February 23, 2020)</h4> 
    <hr /> 
   </div> 
   <div class="section"> 
-   <h4 id="Phoenix_5.1.0_released_February_10_2020"><a class="externalLink" 
href="https://phoenix.apache.org/download.html";>Phoenix 5.1.0 released</a> 
(February 10, 2020)</h4> 
+   <h4 id="Phoenix_5.1.0_released_February_10_2020"><a 
href="download.html">Phoenix 5.1.0 released</a> (February 10, 2020)</h4> 
    <hr /> 
   </div> 
   <div class="section"> 
@@ -207,7 +207,7 @@
    <hr /> 
   </div> 
   <div class="section"> 
-   <h4 id="PhoenixCon_2018_announced_for_June_18th_2018_March_24_2018"><a 
class="externalLink" 
href="https://phoenix.apache.org/phoenixcon-2018";>PhoenixCon 2018 announced for 
June 18th, 2018</a> (March 24, 2018)</h4> 
+   <h4 id="PhoenixCon_2018_announced_for_June_18th_2018_March_24_2018"><a 
href="phoenixcon-2018">PhoenixCon 2018 announced for June 18th, 2018</a> (March 
24, 2018)</h4> 
    <hr /> 
   </div> 
   <div class="section"> 
@@ -251,7 +251,7 @@
    <hr /> 
   </div> 
   <div class="section"> 
-   <h4 id="Announcing_transaction_support_in_4.7.0_release_March_10_2016"><a 
class="externalLink" 
href="http://phoenix.apache.org/transactions.html";>Announcing transaction 
support in 4.7.0 release</a> (March 10, 2016)</h4> 
+   <h4 id="Announcing_transaction_support_in_4.7.0_release_March_10_2016"><a 
href="transactions.html">Announcing transaction support in 4.7.0 release</a> 
(March 10, 2016)</h4> 
    <hr /> 
   </div> 
   <div class="section"> 

Modified: phoenix/site/publish/performance.html
URL: 
http://svn.apache.org/viewvc/phoenix/site/publish/performance.html?rev=1893163&r1=1893162&r2=1893163&view=diff
==============================================================================
--- phoenix/site/publish/performance.html (original)
+++ phoenix/site/publish/performance.html Thu Sep  9 05:55:04 2021
@@ -1,7 +1,7 @@
 
 <!DOCTYPE html>
 <!--
- Generated by Apache Maven Doxia at 2021-08-27
+ Generated by Apache Maven Doxia at 2021-09-08
  Rendered using Reflow Maven Skin 1.1.0 
(http://andriusvelykis.github.io/reflow-maven-skin)
 -->
 <html  xml:lang="en" lang="en">
@@ -169,6 +169,7 @@
 <div class="page-header">
  <h1>Performance</h1>
 </div> 
+<p><span id="alerts" style="background-color:#ffc; text-align: center;display: 
block;padding:10px; border-bottom: solid 1px #cc9"> This page hasn’t been 
updated recently, and may not reflect the current state of the 
project</span></p> 
 <p>Phoenix follows the philosophy of <b>bringing the computation to the 
data</b> by using:</p> 
 <ul> 
  <li><b>coprocessors</b> to perform operations on the server-side thus 
minimizing client/server data transfer</li> 

Modified: phoenix/site/publish/phoenix_spark.html
URL: 
http://svn.apache.org/viewvc/phoenix/site/publish/phoenix_spark.html?rev=1893163&r1=1893162&r2=1893163&view=diff
==============================================================================
--- phoenix/site/publish/phoenix_spark.html (original)
+++ phoenix/site/publish/phoenix_spark.html Thu Sep  9 05:55:04 2021
@@ -1,7 +1,7 @@
 
 <!DOCTYPE html>
 <!--
- Generated by Apache Maven Doxia at 2021-08-27
+ Generated by Apache Maven Doxia at 2021-09-08
  Rendered using Reflow Maven Skin 1.1.0 
(http://andriusvelykis.github.io/reflow-maven-skin)
 -->
 <html  xml:lang="en" lang="en">
@@ -616,7 +616,7 @@ val firstCol = rdd.first()(&quot;COL1&qu
   </div> 
   <div class="section"> 
    <h4 id="Saving_RDDs_to_Phoenix">Saving RDDs to Phoenix</h4> 
-   <p><tt>saveToPhoenix</tt> is an implicit method on RDD[Product], or an RDD 
of Tuples. The data types must correspond to the Java types Phoenix supports 
(<a class="externalLink" 
href="http://phoenix.apache.org/language/datatypes.html";>http://phoenix.apache.org/language/datatypes.html</a>)</p>
 
+   <p><tt>saveToPhoenix</tt> is an implicit method on RDD[Product], or an RDD 
of Tuples. The data types must correspond to the Java types Phoenix supports 
(language/datatypes.html)</p> 
    <p>Given a Phoenix table with the following DDL:</p> 
    <div class="source"> 
     <pre>CREATE TABLE OUTPUT_TEST_TABLE (id BIGINT NOT NULL PRIMARY KEY, col1 
VARCHAR, col2 INTEGER);

Modified: phoenix/site/publish/python.html
URL: 
http://svn.apache.org/viewvc/phoenix/site/publish/python.html?rev=1893163&r1=1893162&r2=1893163&view=diff
==============================================================================
--- phoenix/site/publish/python.html (original)
+++ phoenix/site/publish/python.html Thu Sep  9 05:55:04 2021
@@ -1,7 +1,7 @@
 
 <!DOCTYPE html>
 <!--
- Generated by Apache Maven Doxia at 2021-08-27
+ Generated by Apache Maven Doxia at 2021-09-08
  Rendered using Reflow Maven Skin 1.1.0 
(http://andriusvelykis.github.io/reflow-maven-skin)
 -->
 <html  xml:lang="en" lang="en">
@@ -183,7 +183,7 @@
  </div> 
  <div class="section"> 
   <h3 id="From_source">From source</h3> 
-  <p>You can build phoenixdb from the official source <a class="externalLink" 
href="https://phoenix.apache.org/download.html";>release</a>, or you can use the 
latest development version from the soure <a class="externalLink" 
href="https://phoenix.apache.org/source.html";>repository</a>. The pythondb 
source lives in the <tt>python-phoenixdb</tt> direcory of the 
python-queryserver repository.</p> 
+  <p>You can build phoenixdb from the official source <a 
href=".html">release</a>, or you can use the latest development version from 
the soure <a href="source.html">repository</a>. The pythondb source lives in 
the <tt>python-phoenixdb</tt> direcory of the python-queryserver 
repository.</p> 
   <div class="source"> 
    <pre>$ cd python-phoenixdb # (Only when building from the git repo)
 $ pip install -r requirements.txt

Modified: phoenix/site/publish/recent.html
URL: 
http://svn.apache.org/viewvc/phoenix/site/publish/recent.html?rev=1893163&r1=1893162&r2=1893163&view=diff
==============================================================================
--- phoenix/site/publish/recent.html (original)
+++ phoenix/site/publish/recent.html Thu Sep  9 05:55:04 2021
@@ -1,7 +1,7 @@
 
 <!DOCTYPE html>
 <!--
- Generated by Apache Maven Doxia at 2021-08-27
+ Generated by Apache Maven Doxia at 2021-09-08
  Rendered using Reflow Maven Skin 1.1.0 
(http://andriusvelykis.github.io/reflow-maven-skin)
 -->
 <html  xml:lang="en" lang="en">
@@ -169,12 +169,13 @@
 <div class="page-header">
  <h1>New Features</h1>
 </div> 
+<p><span id="alerts" style="background-color:#ffc; text-align: center;display: 
block;padding:10px; border-bottom: solid 1px #cc9"> This page hasn’t been 
updated recently, and may be missing relevant information for current 
releases</span></p> 
 <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 href="tablesample.html">Table Sampling</a></b>. Support the 
<tt>TABLESAMPLE</tt> clause by implementing a filter that uses the guideposts 
established by stats gathering to only return a percentage of the rows. 
<b>Available in our 4.12 release</b></li> 
- <li><b><a class="externalLink" 
href="https://phoenix.apache.org/columnencoding.html";>Reduce on disk 
storage</a></b>. Reduce on disk storage to improve performance by a) packing 
all values into a single cell per column family and b) provide an indirection 
between the column name and the column qualifier. <b>Available in our 4.10 
release</b></li> 
- <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 href="columnencoding.html">Reduce on disk storage</a></b>. Reduce 
on disk storage to improve performance by a) packing all values into a single 
cell per column family and b) provide an indirection between the column name 
and the column qualifier. <b>Available in our 4.10 release</b></li> 
+ <li><b><a href="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 href="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/release.html
URL: 
http://svn.apache.org/viewvc/phoenix/site/publish/release.html?rev=1893163&r1=1893162&r2=1893163&view=diff
==============================================================================
--- phoenix/site/publish/release.html (original)
+++ phoenix/site/publish/release.html Thu Sep  9 05:55:04 2021
@@ -1,7 +1,7 @@
 
 <!DOCTYPE html>
 <!--
- Generated by Apache Maven Doxia at 2021-08-27
+ Generated by Apache Maven Doxia at 2021-09-08
  Rendered using Reflow Maven Skin 1.1.0 
(http://andriusvelykis.github.io/reflow-maven-skin)
 -->
 <html  xml:lang="en" lang="en">
@@ -273,7 +273,7 @@ mvn versions:set -DnewVersion=4.16.0-HBa
 </pre> 
    </div></li> 
   <li>If releasing Phoenix (core) Create a JIRA to update 
PHOENIX_MAJOR_VERSION, PHOENIX_MINOR_VERSION and PHOENIX_PATCH_NUMBER in 
MetaDataProtocol.java appropriately to next version (4, 16, 0 respectively in 
this case) and compatible_client_versions.json file with the client versions 
that are compatible against the next version ( In this case 4.14.3 and 4.15.0 
would be the backward compatible clients for 4.16.0 ). This Jira should be 
committed/marked with fixVersion of the next release candidate.</li> 
-  <li>Add documentation of released version to the <a class="externalLink" 
href="http://phoenix.apache.org/download.html";>downloads page</a> and <a 
class="externalLink" 
href="https://en.wikipedia.org/wiki/Apache_Phoenix";>wiki</a>.</li> 
+  <li>Add documentation of released version to the <a 
href="download.html">downloads page</a> and <a class="externalLink" 
href="https://en.wikipedia.org/wiki/Apache_Phoenix";>wiki</a>.</li> 
   <li>Send out an announcement email. See example <a class="externalLink" 
href="https://www.mail-archive.com/dev@phoenix.apache.org/msg54764.html";>here</a>.</li>
 
   <li>Bulk close Jiras that were marked for the release fixVersion.</li> 
  </ol> 

Modified: phoenix/site/publish/release_notes.html
URL: 
http://svn.apache.org/viewvc/phoenix/site/publish/release_notes.html?rev=1893163&r1=1893162&r2=1893163&view=diff
==============================================================================
--- phoenix/site/publish/release_notes.html (original)
+++ phoenix/site/publish/release_notes.html Thu Sep  9 05:55:04 2021
@@ -1,7 +1,7 @@
 
 <!DOCTYPE html>
 <!--
- Generated by Apache Maven Doxia at 2021-08-27
+ Generated by Apache Maven Doxia at 2021-09-08
  Rendered using Reflow Maven Skin 1.1.0 
(http://andriusvelykis.github.io/reflow-maven-skin)
 -->
 <html  xml:lang="en" lang="en">
@@ -185,7 +185,7 @@
  </div> 
  <div class="section"> 
   <h3 id="Phoenix-4.8.0_Release_Notes"><u>Phoenix-4.8.0 Release Notes</u></h3> 
-  <p><a class="externalLink" 
href="https://issues.apache.org/jira/browse/PHOENIX-3164";>PHOENIX-3164</a> is a 
relatively serious bug that affects the <a class="externalLink" 
href="http://phoenix.apache.org/server.html";>Phoenix Query Server</a> deployed 
with “security enabled” (Kerberos or Active Directory). Due to another 
late-game change in the 4.8.0 release as well as an issue with the use of 
Hadoop’s UserGroupInformation class, every “client session” to the 
Phoenix Query Server with security enabled will result in a new instance of the 
Phoenix JDBC driver <tt>PhoenixConnection</tt> (and other related classes). 
This ultimately results in a new connection to ZooKeeper for each “client 
session”.</p> 
+  <p><a class="externalLink" 
href="https://issues.apache.org/jira/browse/PHOENIX-3164";>PHOENIX-3164</a> is a 
relatively serious bug that affects the <a href="server.html">Phoenix Query 
Server</a> deployed with “security enabled” (Kerberos or Active Directory). 
Due to another late-game change in the 4.8.0 release as well as an issue with 
the use of Hadoop’s UserGroupInformation class, every “client session” to 
the Phoenix Query Server with security enabled will result in a new instance of 
the Phoenix JDBC driver <tt>PhoenixConnection</tt> (and other related classes). 
This ultimately results in a new connection to ZooKeeper for each “client 
session”.</p> 
   <p>Within a short amount of time of active use with the Phoenix Query Server 
creating a new ZooKeeper connection for each “client session”, the number 
of ZooKeeper connections will have grown rapidly likely triggering 
ZooKeeper’s built-in denial of service protection (<a class="externalLink" 
href="https://zookeeper.apache.org/doc/r3.4.8/zookeeperAdmin.html";>maxClientCnxns</a>).
 This will cause all future connections to ZooKeeper by the host running the 
Phoenix Query Server to be dropped. This would prevent all HBase client API 
calls which need to access ZooKeeper from completing.</p> 
   <p>As part of <a class="externalLink" 
href="https://issues.apache.org/jira/browse/PHOENIX-1734";>PHOENIX-1734</a> we 
have changed the local index implementation to store index data in the separate 
column families in the same data table. So while upgrading the phoenix at 
server we need to remove below local index related configurations from 
<tt>hbase-site.xml</tt> and run upgrade steps mentioned <a 
href="secondary_indexing.html#Upgrading_Local_Indexes_created_before_4.8.0">here</a></p>
 
   <div class="source"> 

Modified: phoenix/site/publish/resources.html
URL: 
http://svn.apache.org/viewvc/phoenix/site/publish/resources.html?rev=1893163&r1=1893162&r2=1893163&view=diff
==============================================================================
--- phoenix/site/publish/resources.html (original)
+++ phoenix/site/publish/resources.html Thu Sep  9 05:55:04 2021
@@ -1,7 +1,7 @@
 
 <!DOCTYPE html>
 <!--
- Generated by Apache Maven Doxia at 2021-08-27
+ Generated by Apache Maven Doxia at 2021-09-08
  Rendered using Reflow Maven Skin 1.1.0 
(http://andriusvelykis.github.io/reflow-maven-skin)
 -->
 <html  xml:lang="en" lang="en">
@@ -169,7 +169,7 @@
 <div class="page-header">
  <h1>Presentations</h1>
 </div> 
-<p>Below are some prior presentations that have been done on Apache Phoenix. 
Another good source of information is the Apache Phoenix <a 
class="externalLink" href="https://blogs.apache.org/phoenix/";>blog</a>.</p> 
+<p>Below are some prior presentations that have been done on Apache Phoenix. 
Another good source of information is the Apache Phoenix <a 
class="externalLink" href="https://blogs.apache.org/phoenix/";>blog</a> and the 
<a href="tech_talks.html">Phoenix Tech Talks</a>.</p> 
 <table border="0" class="bodyTable table table-striped table-hover"> 
  <thead> 
   <tr class="a"> 
@@ -182,7 +182,7 @@
  <tbody> 
   <tr class="b"> 
    <td>Drillix: Apache Phoenix + Apache Drill </td> 
-   <td><a class="externalLink" 
href="http://phoenix.apache.org/presentations/Drillix.pdf";>Slides</a> </td> 
+   <td><a href="presentations/Drillix.pdf">Slides</a> </td> 
    <td>Salesforce.com </td> 
    <td>2016 </td> 
   </tr> 
@@ -194,7 +194,7 @@
   </tr> 
   <tr class="b"> 
    <td>High Performance Clickstream Analytics with Apache HBase/Phoenix </td> 
-   <td><a class="externalLink" 
href="http://phoenix.apache.org/presentations/StrataHadoopWorld.pdf";>Slides</a> 
</td> 
+   <td><a href="presentations/StrataHadoopWorld.pdf">Slides</a> </td> 
    <td>Strata + Hadoop World </td> 
    <td>2016 </td> 
   </tr> 
@@ -206,13 +206,13 @@
   </tr> 
   <tr class="b"> 
    <td>Lightning Talk for Apache Phoenix </td> 
-   <td><a class="externalLink" 
href="http://phoenix.apache.org/presentations/HPTS.pdf";>Slides</a> </td> 
+   <td><a href="presentations/HPTS.pdf">Slides</a> </td> 
    <td>HPTS </td> 
    <td>2015 </td> 
   </tr> 
   <tr class="a"> 
    <td>Tuning Phoenix and HBase for OLTP </td> 
-   <td><a class="externalLink" 
href="http://phoenix.apache.org/presentations/TuningForOLTP.pdf";>Slides</a> 
</td> 
+   <td><a href="presentations/TuningForOLTP.pdf">Slides</a> </td> 
    <td>Tuning Presentation </td> 
    <td>2015 </td> 
   </tr> 
@@ -224,43 +224,43 @@
   </tr> 
   <tr class="a"> 
    <td>Apache Phoenix: The Evolution of a Relational Database Layer over HBase 
</td> 
-   <td><a class="externalLink" 
href="http://phoenix.apache.org/presentations/HBaseCon2015-16x9.pdf";>Slides</a> 
</td> 
+   <td><a href="presentations/HBaseCon2015-16x9.pdf">Slides</a> </td> 
    <td>HBaseCon </td> 
    <td>2015 </td> 
   </tr> 
   <tr class="b"> 
    <td>Apache Phoenix: Transforming HBase into a Relational Database </td> 
-   <td><a class="externalLink" 
href="http://phoenix.apache.org/presentations/OC-HUG-2014-10-4x3.pdf";>Slides</a>
 </td> 
+   <td><a href="presentations/OC-HUG-2014-10-4x3.pdf">Slides</a> </td> 
    <td>OC Hadoop User Group </td> 
    <td>2014 </td> 
   </tr> 
   <tr class="a"> 
    <td>Apache Phoenix: Transforming HBase into a SQL database </td> 
-   <td><a class="externalLink" 
href="http://phoenix.apache.org/presentations/HadoopSummit2014-16x9.pdf";>Slides</a>,
 <a class="externalLink" 
href="https://www.youtube.com/watch?v=f4Nmh5KM6gI&amp;feature=youtu.be";>Video</a>
 </td> 
+   <td><a href="presentations/HadoopSummit2014-16x9.pdf">Slides</a>, <a 
class="externalLink" 
href="https://www.youtube.com/watch?v=f4Nmh5KM6gI&amp;feature=youtu.be";>Video</a>
 </td> 
    <td>Hadoop Summit </td> 
    <td>2014 </td> 
   </tr> 
   <tr class="b"> 
    <td>Taming HBase with Apache Phoenix and SQL </td> 
-   <td><a class="externalLink" 
href="http://phoenix.apache.org/presentations/HBaseCon2014-16x9.pdf";>Slides</a>,
 <a class="externalLink" href="http://vimeo.com/98485780";>Video</a> </td> 
+   <td><a href="presentations/HBaseCon2014-16x9.pdf">Slides</a>, <a 
class="externalLink" href="http://vimeo.com/98485780";>Video</a> </td> 
    <td>HBaseCon </td> 
    <td>2014 </td> 
   </tr> 
   <tr class="a"> 
    <td>How Apache Phoenix enables interactive, low latency applications over 
HBase </td> 
-   <td><a class="externalLink" 
href="http://phoenix.apache.org/presentations/ApacheCon2014-16x9.pdf";>Slides</a>,
 <a class="externalLink" 
href="https://www.youtube.com/watch?v=9qfBnFyKZwM";>Video</a> </td> 
+   <td><a href="presentations/ApacheCon2014-16x9.pdf">Slides</a>, <a 
class="externalLink" 
href="https://www.youtube.com/watch?v=9qfBnFyKZwM";>Video</a> </td> 
    <td>ApacheCon </td> 
    <td>2014 </td> 
   </tr> 
   <tr class="b"> 
    <td>How (and why) Phoenix puts the SQL back into NoSQL </td> 
-   <td><a class="externalLink" 
href="http://phoenix.apache.org/presentations/HadoopSummit2013-16x9.pdf";>Slides</a>,
 <a class="externalLink" 
href="http://www.youtube.com/watch?v=YHsHdQ08trg";>Video</a> </td> 
+   <td><a href="presentations/HadoopSummit2013-16x9.pdf">Slides</a>, <a 
class="externalLink" 
href="http://www.youtube.com/watch?v=YHsHdQ08trg";>Video</a> </td> 
    <td>Hadoop Summit </td> 
    <td>2013 </td> 
   </tr> 
   <tr class="a"> 
    <td>How (and why) Phoenix puts the SQL back into NoSQL </td> 
-   <td><a class="externalLink" 
href="http://phoenix.apache.org/presentations/HBaseCon2013-4x3.pdf";>Slides</a>, 
<a class="externalLink" 
href="http://www.cloudera.com/content/cloudera/en/resources/library/hbasecon/hbasecon-2013--how-and-why-phoenix-puts-the-sql-back-into-nosql-video.html";>Video</a>
 </td> 
+   <td><a href="presentations/HBaseCon2013-4x3.pdf">Slides</a>, <a 
class="externalLink" 
href="http://www.cloudera.com/content/cloudera/en/resources/library/hbasecon/hbasecon-2013--how-and-why-phoenix-puts-the-sql-back-into-nosql-video.html";>Video</a>
 </td> 
    <td>HBaseCon </td> 
    <td>2013 </td> 
   </tr> 
@@ -269,8 +269,8 @@
 <div class="section"> 
  <h2 id="PhoenixCon">PhoenixCon</h2> 
  <p>PhoenixCon is a developer-focused event available to the public. The event 
is comprised of users and developers giving presentations about how they are 
using Apache Phoenix or new features coming to the project.</p> 
- <p>For previous presentations given at PhoenixCon events, please refer to the 
<a class="externalLink" 
href="https://phoenix.apache.org/phoenixcon-archives.html";>archives</a>.</p> 
- <p>See the following for more information about <a class="externalLink" 
href="https://phoenix.apache.org/phoenixcon-2018/";>PhoenixCon 2018</a>.</p> 
+ <p>For previous presentations given at PhoenixCon events, please refer to the 
<a href="phoenixcon-archives.html">archives</a>.</p> 
+ <p>See the following for more information about <a 
href="phoenixcon-2018/">PhoenixCon 2018</a>.</p> 
 </div>
                        </div>
                </div>

Modified: phoenix/site/publish/roadmap.html
URL: 
http://svn.apache.org/viewvc/phoenix/site/publish/roadmap.html?rev=1893163&r1=1893162&r2=1893163&view=diff
==============================================================================
--- phoenix/site/publish/roadmap.html (original)
+++ phoenix/site/publish/roadmap.html Thu Sep  9 05:55:04 2021
@@ -1,7 +1,7 @@
 
 <!DOCTYPE html>
 <!--
- Generated by Apache Maven Doxia at 2021-08-27
+ Generated by Apache Maven Doxia at 2021-09-08
  Rendered using Reflow Maven Skin 1.1.0 
(http://andriusvelykis.github.io/reflow-maven-skin)
 -->
 <html  xml:lang="en" lang="en">
@@ -169,6 +169,7 @@
 <div class="page-header">
  <h1>Roadmap</h1>
 </div> 
+<p><span id="alerts" style="background-color:#ffc; text-align: center;display: 
block;padding:10px; border-bottom: solid 1px #cc9"> This page hasn’t been 
updated recently, and may not reflect the current state of the 
project</span></p> 
 <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><a class="externalLink" 
href="https://issues.apache.org/jira/browse/PHOENIX-3146";>Stress and chaos 
testing</a></b>. Open source and automate the running of stress and chaos tests 
that exercise Phoenix and HBase under high load and failure conditions.</li> 

Modified: phoenix/site/publish/secondary_indexing.html
URL: 
http://svn.apache.org/viewvc/phoenix/site/publish/secondary_indexing.html?rev=1893163&r1=1893162&r2=1893163&view=diff
==============================================================================
--- phoenix/site/publish/secondary_indexing.html (original)
+++ phoenix/site/publish/secondary_indexing.html Thu Sep  9 05:55:04 2021
@@ -1,7 +1,7 @@
 
 <!DOCTYPE html>
 <!--
- Generated by Apache Maven Doxia at 2021-08-27
+ Generated by Apache Maven Doxia at 2021-09-08
  Rendered using Reflow Maven Skin 1.1.0 
(http://andriusvelykis.github.io/reflow-maven-skin)
 -->
 <html  xml:lang="en" lang="en">
@@ -338,9 +338,9 @@ CREATE LOCAL INDEX my_index ON my_table
     <li>Delete the data table rows</li> 
     <li>Delete index table rows</li> 
    </ol> 
-   <p>See <a class="externalLink" 
href="http://phoenix.apache.org/secondary_indexing.html#Resources";>resources</a>
 for more in-depth information.</p> 
+   <p>See <a href="secondary_indexing.html#Resources">resources</a> for more 
in-depth information.</p> 
    <p>All newly created tables use the new indexing algorithm.</p> 
-   <p>Indexes created with older Phoenix versions will continue to use the old 
implementation, until upgraded with <a class="externalLink" 
href="http://phoenix.apache.org/secondary_indexing.html#Index_Upgrade_Tool";>IndexUpgradeTool</a></p>
 
+   <p>Indexes created with older Phoenix versions will continue to use the old 
implementation, until upgraded with <a 
href="secondary_indexing.html#Index_Upgrade_Tool">IndexUpgradeTool</a></p> 
   </div> 
   <div class="section"> 
    <h4 id="Mutable_table_indexes_for_4.14_and_5.0_and_older_versions">Mutable 
table indexes for 4.14 (and 5.0) and older versions</h4> 
@@ -387,7 +387,7 @@ CREATE LOCAL INDEX my_index ON my_table
    </div> 
    <div class="section"> 
     <h5 
id="Disable_mutable_index_on_write_failure_with_manual_rebuild_required">Disable
 mutable index on write failure with manual rebuild required</h5> 
-    <p>This is the lowest level of consistency for mutable secondary indexes. 
In this case, when a write to a secondary index fails, the index will be marked 
as disabled with a manual <a class="externalLink" 
href="http://phoenix.apache.org/language/index.html#alter_index";>rebuild of the 
index</a> required to enable it to be used once again by queries.</p> 
+    <p>This is the lowest level of consistency for mutable secondary indexes. 
In this case, when a write to a secondary index fails, the index will be marked 
as disabled with a manual <a href="language/index.html#alter_index">rebuild of 
the index</a> required to enable it to be used once again by queries.</p> 
     <p>The following server-side configurations controls this behavior:</p> 
     <ul> 
      <li><tt>phoenix.index.failure.handling.rebuild</tt> must be set to false 
to disable a mutable index from being rebuilt in the background in the event of 
a commit failure.</li> 
@@ -460,7 +460,7 @@ CREATE LOCAL INDEX my_index ON my_table
  </div> 
  <div class="section"> 
   <h3 id="Upgrading_Local_Indexes_created_before_4.8.0">Upgrading Local 
Indexes created before 4.8.0</h3> 
-  <p>While upgrading the Phoenix to 4.8.0+ version at server remove above 
three local indexing related configurations from <tt>hbase-site.xml</tt> if 
present. From client we are supporting both online(while initializing the 
connection from phoenix client of 4.8.0+ versions) and offline(using psql tool) 
upgrade of local indexes created before 4.8.0. As part of upgrade we recreate 
the local indexes in ASYNC mode. After upgrade user need to build the indexes 
using <a class="externalLink" 
href="http://phoenix.apache.org/secondary_indexing.html#Index_Population";>IndexTool</a></p>
 
+  <p>While upgrading the Phoenix to 4.8.0+ version at server remove above 
three local indexing related configurations from <tt>hbase-site.xml</tt> if 
present. From client we are supporting both online(while initializing the 
connection from phoenix client of 4.8.0+ versions) and offline(using psql tool) 
upgrade of local indexes created before 4.8.0. As part of upgrade we recreate 
the local indexes in ASYNC mode. After upgrade user need to build the indexes 
using <a href="secondary_indexing.html#Index_Population">IndexTool</a></p> 
   <p>Following client side configuration used in the upgrade.</p> 
   <ol style="list-style-type: decimal"> 
    <li><tt>phoenix.client.localIndexUpgrade</tt> 

Modified: phoenix/site/publish/sequences.html
URL: 
http://svn.apache.org/viewvc/phoenix/site/publish/sequences.html?rev=1893163&r1=1893162&r2=1893163&view=diff
==============================================================================
--- phoenix/site/publish/sequences.html (original)
+++ phoenix/site/publish/sequences.html Thu Sep  9 05:55:04 2021
@@ -1,7 +1,7 @@
 
 <!DOCTYPE html>
 <!--
- Generated by Apache Maven Doxia at 2021-08-27
+ Generated by Apache Maven Doxia at 2021-09-08
  Rendered using Reflow Maven Skin 1.1.0 
(http://andriusvelykis.github.io/reflow-maven-skin)
 -->
 <html  xml:lang="en" lang="en">
@@ -174,7 +174,7 @@
  <pre>CREATE SEQUENCE my_schema.my_sequence;
 </pre>
 </div> 
-<p>This will create a sequence named <tt>my_schema.my_sequence</tt> with the 
an initial sequence value of 1, incremented by 1 each time, with no cycle, 
minimum value or maximum value, and 100 sequence values cached on your session 
(determined by the <tt>phoenix.sequence.cacheSize</tt> config parameter). The 
complete syntax of <tt>CREATE SEQUENCE</tt> may be found <a 
class="externalLink" 
href="http://phoenix.apache.org/language/index.html#create_sequence";>here</a>.</p>
 
+<p>This will create a sequence named <tt>my_schema.my_sequence</tt> with the 
an initial sequence value of 1, incremented by 1 each time, with no cycle, 
minimum value or maximum value, and 100 sequence values cached on your session 
(determined by the <tt>phoenix.sequence.cacheSize</tt> config parameter). The 
complete syntax of <tt>CREATE SEQUENCE</tt> may be found <a 
href="language/index.html#create_sequence">here</a>.</p> 
 <p>Caching sequence values on your session improves performance, as we don’t 
need to ask the server for more sequence values until we run out of cached 
values. The tradeoff is that you may end up with gaps in your sequence values 
when other sessions also use the same sequence.</p> 
 <p>All of these parameters can be overridden when the sequence is created like 
this:</p> 
 <div class="source"> 

Modified: phoenix/site/publish/server.html
URL: 
http://svn.apache.org/viewvc/phoenix/site/publish/server.html?rev=1893163&r1=1893162&r2=1893163&view=diff
==============================================================================
--- phoenix/site/publish/server.html (original)
+++ phoenix/site/publish/server.html Thu Sep  9 05:55:04 2021
@@ -1,7 +1,7 @@
 
 <!DOCTYPE html>
 <!--
- Generated by Apache Maven Doxia at 2021-08-27
+ Generated by Apache Maven Doxia at 2021-09-08
  Rendered using Reflow Maven Skin 1.1.0 
(http://andriusvelykis.github.io/reflow-maven-skin)
 -->
 <html  xml:lang="en" lang="en">
@@ -178,7 +178,7 @@
  <div class="section"> 
   <h3 id="Clients">Clients</h3> 
   <p>The primary client implementation is currently a JDBC driver with minimal 
dependencies. The default and primary transport mechanism since Phoenix 4.7 is 
Protobuf, the older JSON mechanism can still be enabled. The distribution 
includes the sqlline-thin.py CLI client that uses the JDBC thin client.</p> 
-  <p>The Phoenix project also maintains the Python driver <a 
class="externalLink" 
href="https://phoenix.apache.org/python.html";>phoenixdb</a>.</p> 
+  <p>The Phoenix project also maintains the Python driver <a 
href="python.html">phoenixdb</a>.</p> 
   <p>The Avatica <a class="externalLink" 
href="https://calcite.apache.org/avatica/docs/go_client_reference.html";>Go 
client</a> can also be used.</p> 
   <p>Proprietary ODBC drivers are also available for Windows and Linux.</p> 
  </div> 
@@ -187,7 +187,7 @@
  <h2 id="Installation">Installation</h2> 
  <p>In the 4.4-4.14 and 5.0 releases the query server and its JDBC client are 
part of the standard Phoenix distribution. They require no additional 
dependencies or installation.</p> 
  <p>After the 4.15 and 5.1 release, the query server has been unbundled into 
the phoenix-queryserver repository, and its version number has been reset to 
6.0.</p> 
- <p>Download the latest source or binary release from the <a 
class="externalLink" href="https://phoenix.apache.org/download.html";>Download 
page</a>, or check out the development version from <a class="externalLink" 
href="https://github.com/apache/phoenix-queryserver";>github</a></p> 
+ <p>Download the latest source or binary release from the <a 
href="/download.html">Download page</a>, or check out the development version 
from <a class="externalLink" 
href="https://github.com/apache/phoenix-queryserver";>github</a></p> 
  <p>Either unpack the binary distribution, or build it from source. See 
BUILDING.md in the source distribution on how to build.</p> 
 </div> 
 <div class="section"> 
@@ -251,7 +251,7 @@
 </div> 
 <div class="section"> 
  <h2 id="Metrics">Metrics</h2> 
- <p>By default, the Phoenix Query Server exposes various Phoenix global client 
metrics via JMX (for HBase versions 1.3 and up). The list of metrics are 
available <a class="externalLink" 
href="https://phoenix.apache.org/metrics.html";>here</a>.</p> 
+ <p>By default, the Phoenix Query Server exposes various Phoenix global client 
metrics via JMX (for HBase versions 1.3 and up). The list of metrics are 
available <a href="metrics.html">here</a>.</p> 
  <p>PQS Metrics use <a class="externalLink" 
href="https://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-common/Metrics.html";>Hadoop
 Metrics 2</a> internally for metrics publishing. Hence it publishes various 
JVM related metrics. Metrics can be filtered based on certain tags, which can 
be configured by the property specified in hbase-site.xml on the classpath. 
Further details are provided in Configuration section.</p> 
 </div> 
 <div class="section"> 

Modified: phoenix/site/publish/tuning_guide.html
URL: 
http://svn.apache.org/viewvc/phoenix/site/publish/tuning_guide.html?rev=1893163&r1=1893162&r2=1893163&view=diff
==============================================================================
--- phoenix/site/publish/tuning_guide.html (original)
+++ phoenix/site/publish/tuning_guide.html Thu Sep  9 05:55:04 2021
@@ -1,7 +1,7 @@
 
 <!DOCTYPE html>
 <!--
- Generated by Apache Maven Doxia at 2021-08-27
+ Generated by Apache Maven Doxia at 2021-09-08
  Rendered using Reflow Maven Skin 1.1.0 
(http://andriusvelykis.github.io/reflow-maven-skin)
 -->
 <html  xml:lang="en" lang="en">
@@ -204,7 +204,7 @@
    <li>For write-heavy data: 
     <ul> 
      <li>Pre-split the table. It can be helpful to split the table into 
pre-defined regions, or if the keys are monotonically increasing use salting to 
to avoid creating write hotspots on a small number of nodes. Use real data 
types rather than raw byte data.</li> 
-     <li>Create local indexes. Reads from local indexes have a performance 
penalty, so it’s important to do performance testing. See the <a 
class="externalLink" href="https://phoenix.apache.org/pherf.html";>Pherf</a> 
tool.</li> 
+     <li>Create local indexes. Reads from local indexes have a performance 
penalty, so it’s important to do performance testing. See the <a 
href="pherf.html">Pherf</a> tool.</li> 
     </ul></li> 
   </ul> 
  </div> 
@@ -220,11 +220,11 @@
  <div class="section"> 
   <h3 id="Can_the_data_be_append-only_immutable">Can the data be append-only 
(immutable)?</h3> 
   <ul> 
-   <li>If the data is immutable or append-only, declare the table and its 
indexes as immutable using the <tt>IMMUTABLE_ROWS</tt> <a class="externalLink" 
href="http://phoenix.apache.org/language/index.html#options";>option</a> at 
creation time to reduce the write-time cost. If you need to make an existing 
table immutable, you can do so with <tt>ALTER TABLE trans.event SET 
IMMUTABLE_ROWS=true</tt> after creation time. 
+   <li>If the data is immutable or append-only, declare the table and its 
indexes as immutable using the <tt>IMMUTABLE_ROWS</tt> <a 
href="language/index.html#options">option</a> at creation time to reduce the 
write-time cost. If you need to make an existing table immutable, you can do so 
with <tt>ALTER TABLE trans.event SET IMMUTABLE_ROWS=true</tt> after creation 
time. 
     <ul> 
-     <li>If speed is more important than data integrity, you can use the 
<tt>DISABLE_WAL</tt> <a class="externalLink" 
href="http://phoenix.apache.org/language/index.html#options";>option</a>. Note: 
it is possible to lose data with <tt>DISABLE_WAL</tt> if a region server 
fails.</li> 
+     <li>If speed is more important than data integrity, you can use the 
<tt>DISABLE_WAL</tt> <a href="language/index.html#options">option</a>. Note: it 
is possible to lose data with <tt>DISABLE_WAL</tt> if a region server 
fails.</li> 
     </ul></li> 
-   <li>Set the <tt>UPDATE_CACHE_FREQUENCY</tt> <a class="externalLink" 
href="http://phoenix.apache.org/language/index.html#options";>option</a> to 15 
minutes or so if your metadata doesn’t change very often. This property 
determines how often an RPC is done to ensure you’re seeing the latest 
schema.</li> 
+   <li>Set the <tt>UPDATE_CACHE_FREQUENCY</tt> <a 
href="language/index.html#options">option</a> to 15 minutes or so if your 
metadata doesn’t change very often. This property determines how often an RPC 
is done to ensure you’re seeing the latest schema.</li> 
    <li>If the data is not sparse (over 50% of the cells have values), use the 
SINGLE_CELL_ARRAY_WITH_OFFSETS data encoding scheme introduced in Phoenix 4.10, 
which obtains faster performance by reducing the size of the data. For more 
information, see “<a class="externalLink" 
href="https://blogs.apache.org/phoenix/entry/column-mapping-and-immutable-data";>Column
 Mapping and Immutable Data Encoding</a>” on the Apache Phoenix blog.</li> 
   </ul> 
  </div> 
@@ -232,14 +232,14 @@
   <h3 id="Is_the_table_very_large">Is the table very large?</h3> 
   <ul> 
    <li>Use the <tt>ASYNC</tt> keyword with your <tt>CREATE INDEX</tt> call to 
create the index asynchronously via MapReduce job. You’ll need to manually 
start the job; see <a class="externalLink" 
href="https://phoenix.apache.org/secondary_indexing.html#Index_Population";>https://phoenix.apache.org/secondary_indexing.html#Index_Population</a>
 for details.</li> 
-   <li>If the data is too large to scan the table completely, use primary keys 
to create an underlying composite row key that makes it easy to return a subset 
of the data or facilitates <a class="externalLink" 
href="https://phoenix.apache.org/skip_scan.html";>skip-scanning</a>—Phoenix 
can jump directly to matching keys when the query includes key sets in the 
predicate.</li> 
+   <li>If the data is too large to scan the table completely, use primary keys 
to create an underlying composite row key that makes it easy to return a subset 
of the data or facilitates <a href="skip_scan.html">skip-scanning</a>—Phoenix 
can jump directly to matching keys when the query includes key sets in the 
predicate.</li> 
   </ul> 
  </div> 
  <div class="section"> 
   <h3 id="Is_transactionality_required">Is transactionality required?</h3> 
   <p>A transaction is a data operation that is atomic—that is, guaranteed to 
succeed completely or not at all. For example, if you need to make cross-row 
updates to a data table, then you should consider your data transactional.</p> 
   <ul> 
-   <li>If you need transactionality, use the <tt>TRANSACTIONAL</tt> <a 
class="externalLink" 
href="http://phoenix.apache.org/language/index.html#options";>option</a>. (See 
also <a class="externalLink" 
href="http://phoenix.apache.org/transactions.html.";>http://phoenix.apache.org/transactions.html.</a>)</li>
 
+   <li>If you need transactionality, use the <tt>TRANSACTIONAL</tt> <a 
href="language/index.html#options">option</a>. (See also <a 
class="externalLink" 
href="http://phoenix.apache.org/transactions.html.";>http://phoenix.apache.org/transactions.html.</a>)</li>
 
   </ul> 
  </div> 
  <div class="section"> 
@@ -257,7 +257,7 @@
 </div> 
 <div class="section"> 
  <h2 id="Column_Families">Column Families</h2> 
- <p>If some columns are accessed more frequently than others, <a 
class="externalLink" 
href="https://phoenix.apache.org/faq.html#Are_there_any_tips_for_optimizing_Phoenix";>create
 multiple column families</a> to separate the frequently-accessed columns from 
rarely-accessed columns. This improves performance because HBase reads only the 
column families specified in the query.</p> 
+ <p>If some columns are accessed more frequently than others, <a 
href="faq.html#Are_there_any_tips_for_optimizing_Phoenix">create multiple 
column families</a> to separate the frequently-accessed columns from 
rarely-accessed columns. This improves performance because HBase reads only the 
column families specified in the query.</p> 
 </div> 
 <div class="section"> 
  <h2 id="Columns">Columns</h2> 
@@ -270,19 +270,19 @@
  </ul> 
  <h1>Indexes</h1> 
  <p>A Phoenix index is a physical table that stores a pivoted copy of some or 
all of the data in the main table, to serve specific kinds of queries. When you 
issue a query, Phoenix selects the best index for the query automatically. The 
primary index is created automatically based on the primary keys you select. 
You can create secondary indexes, specifying which columns are included based 
on the anticipated queries the index will support.</p> 
- <p>See also: <a class="externalLink" 
href="https://phoenix.apache.org/secondary_indexing.html";>Secondary 
Indexing</a></p> 
+ <p>See also: <a href="secondary_indexing.html">Secondary Indexing</a></p> 
 </div> 
 <div class="section"> 
  <h2 id="Secondary_indexes">Secondary indexes</h2> 
- <p>Secondary indexes can improve read performance by turning what would 
normally be a full table scan into a point lookup (at the cost of storage space 
and write speed). Secondary indexes can be added or removed after table 
creation and don’t require changes to existing queries – queries simply run 
faster. A small number of secondary indexes is often sufficient. Depending on 
your needs, consider creating <i><a class="externalLink" 
href="http://phoenix.apache.org/secondary_indexing.html#Covered_Indexes";>covered</a></i>
 indexes or <i><a class="externalLink" 
href="http://phoenix.apache.org/secondary_indexing.html#Functional_Indexes";>functional</a></i>
 indexes, or both.</p> 
+ <p>Secondary indexes can improve read performance by turning what would 
normally be a full table scan into a point lookup (at the cost of storage space 
and write speed). Secondary indexes can be added or removed after table 
creation and don’t require changes to existing queries – queries simply run 
faster. A small number of secondary indexes is often sufficient. Depending on 
your needs, consider creating <i><a 
href="secondary_indexing.html#Covered_Indexes">covered</a></i> indexes or <i><a 
href="secondary_indexing.html#Functional_Indexes">functional</a></i> indexes, 
or both.</p> 
  <p>If your table is large, use the <tt>ASYNC</tt> keyword with <tt>CREATE 
INDEX</tt> to create the index asynchronously. In this case, the index will be 
built through MapReduce, which means that the client going up or down won’t 
impact index creation and the job is retried automatically if necessary. 
You’ll need to manually start the job, which you can then monitor just as you 
would any other MapReduce job.</p> 
  <p>Example: <tt>create index if not exists event_object_id_idx_b on 
trans.event (object_id) ASYNC UPDATE_CACHE_FREQUENCY=60000;</tt></p> 
- <p>See <a class="externalLink" 
href="https://phoenix.apache.org/secondary_indexing.html#Index_Population";>Index
 Population</a> for details.</p> 
+ <p>See <a href="secondary_indexing.html#Index_Population">Index 
Population</a> for details.</p> 
  <p>If you can’t create the index asynchronously for some reason, then 
increase the query timeout (<tt>phoenix.query.timeoutMs</tt>) to be larger than 
the time it’ll take to build the index. If the <tt>CREATE INDEX</tt> call 
times out or the client goes down before it’s finished, then the index build 
will stop and must be run again. You can monitor the index table as it is 
created—you’ll see new regions created as splits occur. You can query the 
<tt>SYSTEM.STATS</tt> table, which gets populated as splits and compactions 
happen. You can also run a <tt>count(*)</tt> query directly against the index 
table, though that puts more load on your system because requires a full table 
scan.</p> 
  <p>Tips:</p> 
  <ul> 
-  <li>Create <a class="externalLink" 
href="https://phoenix.apache.org/secondary_indexing.html#Local_Indexes";>local</a>
 indexes for write-heavy use cases.</li> 
-  <li>Create global indexes for read-heavy use cases. To save read-time 
overhead, consider creating <a class="externalLink" 
href="https://phoenix.apache.org/secondary_indexing.html#Covered_Indexes";>covered</a>
 indexes.</li> 
+  <li>Create <a href="secondary_indexing.html#Local_Indexes">local</a> indexes 
for write-heavy use cases.</li> 
+  <li>Create global indexes for read-heavy use cases. To save read-time 
overhead, consider creating <a 
href="secondary_indexing.html#Covered_Indexes">covered</a> indexes.</li> 
   <li>If the primary key is monotonically increasing, create salt buckets. The 
salt buckets can’t be changed later, so design them to handle future growth. 
Salt buckets help avoid write hotspots, but can decrease overall throughput due 
to the additional scans needed on read.</li> 
   <li>Set up a cron job to build indexes. Use <tt>ASYNC</tt> with <tt>CREATE 
INDEX</tt> to avoid blocking.</li> 
   <li>Only create the indexes you need.</li> 
@@ -324,7 +324,7 @@
    <li>If necessary, you can do bigger joins with the <tt>/*+ 
USE_SORT_MERGE_JOIN */</tt> hint, but a big join will be an expensive operation 
over huge numbers of rows.</li> 
    <li>If the overall size of all right-hand-side tables would exceed the 
memory size limit, use the <tt>/*+ NO_STAR_JOIN */</tt>hint.</li> 
   </ul> 
-  <p>See also: <a class="externalLink" 
href="https://phoenix.apache.org/language/#hint";>Hint</a>.</p> 
+  <p>See also: <a href="language/#hint">Hint</a>.</p> 
  </div> 
  <div class="section"> 
   <h3 id="Explain_Plans">Explain Plans</h3> 
@@ -332,7 +332,7 @@
  </div> 
  <div class="section"> 
   <h3 id="Parallelization">Parallelization</h3> 
-  <p>You can improve parallelization with the <a class="externalLink" 
href="https://phoenix.apache.org/update_statistics.html";>UPDATE STATISTICS</a> 
command. This command subdivides each region by determining keys called 
<i>guideposts</i> that are equidistant from each other, then uses these 
guideposts to break up queries into multiple parallel scans. Statistics are 
turned on by default. With Phoenix 4.9, the user can set guidepost width for 
each table. Optimal guidepost width depends on a number of factors such as 
cluster size, cluster usage, number of cores per node, table size, and disk 
I/O.</p> 
+  <p>You can improve parallelization with the <a 
href="update_statistics.html">UPDATE STATISTICS</a> command. This command 
subdivides each region by determining keys called <i>guideposts</i> that are 
equidistant from each other, then uses these guideposts to break up queries 
into multiple parallel scans. Statistics are turned on by default. With Phoenix 
4.9, the user can set guidepost width for each table. Optimal guidepost width 
depends on a number of factors such as cluster size, cluster usage, number of 
cores per node, table size, and disk I/O.</p> 
   <p>In Phoenix 4.12, we have added a new configuration 
<tt>phoenix.use.stats.parallelization</tt> that controls whether statistics 
should be used for driving parallelization. Note that one can still run stats 
collection. The information collected is used to surface estimates on number of 
bytes and rows a query will scan when an EXPLAIN is generated for it. </p> 
  </div> 
 </div> 


Reply via email to