You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@phoenix.apache.org by ja...@apache.org on 2014/12/12 05:07:51 UTC
svn commit: r1644823 [2/2] - in /phoenix/site: publish/ publish/language/
source/src/site/ source/src/site/markdown/
Added: phoenix/site/publish/upgrading.html
URL: http://svn.apache.org/viewvc/phoenix/site/publish/upgrading.html?rev=1644823&view=auto
==============================================================================
--- phoenix/site/publish/upgrading.html (added)
+++ phoenix/site/publish/upgrading.html Fri Dec 12 04:07:50 2014
@@ -0,0 +1,366 @@
+
+<!DOCTYPE html>
+<!--
+ Generated by Apache Maven Doxia at 2014-12-11
+ 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>Upgrading Phoenix | 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" />
+
+ <link href="http://netdna.bootstrapcdn.com/bootswatch/2.3.2/flatly/bootstrap.min.css" rel="stylesheet" />
+ <link href="http://netdna.bootstrapcdn.com/twitter-bootstrap/2.3.1/css/bootstrap-responsive.min.css" rel="stylesheet" />
+ <link href="./css/bootswatch.css" rel="stylesheet" />
+ <link href="./css/reflow-skin.css" rel="stylesheet" />
+
+ <link href="http://yandex.st/highlightjs/7.5/styles/default.min.css" rel="stylesheet" />
+
+ <link href="./css/lightbox.css" rel="stylesheet" />
+
+ <link href="./css/site.css" rel="stylesheet" />
+ <link href="./css/print.css" rel="stylesheet" media="print" />
+
+ <!-- Le HTML5 shim, for IE6-8 support of HTML5 elements -->
+ <!--[if lt IE 9]>
+ <script src="http://html5shim.googlecode.com/svn/trunk/html5.js"></script>
+ <![endif]-->
+
+
+
+ </head>
+
+ <body class="page-upgrading project-phoenix-site" data-spy="scroll" data-offset="60" data-target="#toc-scroll-target">
+
+ <div class="navbar navbar-fixed-top">
+ <div class="navbar-inner">
+ <div class="container">
+ <a class="btn btn-navbar" data-toggle="collapse" data-target="#top-nav-collapse">
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ </a>
+ <a class="brand" href="index.html"><div class="xtoplogo"></div></a>
+ <div class="nav-collapse collapse" id="top-nav-collapse">
+ <ul class="nav pull-right">
+ <li class="dropdown">
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown">About <b class="caret"></b></a>
+ <ul class="dropdown-menu">
+ <li ><a href="index.html" title="Overview">Overview</a></li>
+ <li ><a href="recent.html" title="New Features">New Features</a></li>
+ <li ><a href="roadmap.html" title="Roadmap">Roadmap</a></li>
+ <li ><a href="performance.html" title="Performance">Performance</a></li>
+ <li ><a href="team.html" title="Team">Team</a></li>
+ <li ><a href="contributing.html" title="Contributing">Contributing</a></li>
+ <li ><a href="resources.html" title="Resources">Resources</a></li>
+ <li ><a href="mailing_list.html" title="Mailing Lists">Mailing Lists</a></li>
+ <li ><a href="source.html" title="Source Repository">Source Repository</a></li>
+ <li ><a href="issues.html" title="Issue Tracking">Issue Tracking</a></li>
+ <li ><a href="download.html" title="Download">Download</a></li>
+ <li class="divider"/>
+ <li ><a href="release.html" title="How to release">How to release</a></li>
+ <li ><a href="building_website.html" title="How to update website">How to update website</a></li>
+ <li class="divider"/>
+ <li ><a href="http://www.apache.org/licenses/" title="License" class="externalLink">License</a></li>
+ <li ><a href="http://www.apache.org/foundation/sponsorship.html" title="Sponsorship" class="externalLink">Sponsorship</a></li>
+ <li ><a href="http://www.apache.org/foundation/thanks.html" title="Thanks" class="externalLink">Thanks</a></li>
+ <li ><a href="http://www.apache.org/security/" title="Security" class="externalLink">Security</a></li>
+ </ul>
+ </li>
+ <li class="dropdown">
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown">Using <b class="caret"></b></a>
+ <ul class="dropdown-menu">
+ <li ><a href="faq.html" title="F.A.Q.">F.A.Q.</a></li>
+ <li ><a href="Phoenix-in-15-minutes-or-less.html" title="Quick Start">Quick Start</a></li>
+ <li ><a href="building.html" title="Building">Building</a></li>
+ <li ><a href="tuning.html" title="Tuning">Tuning</a></li>
+ <li class="active"><a href="" title="Upgrading">Upgrading</a></li>
+ <li class="divider"/>
+ <li ><a href="secondary_indexing.html" title="Secondary Indexes">Secondary Indexes</a></li>
+ <li ><a href="joins.html" title="Joins">Joins</a></li>
+ <li ><a href="subqueries.html" title="Subqueries">Subqueries</a></li>
+ <li ><a href="views.html" title="Views">Views</a></li>
+ <li ><a href="multi-tenancy.html" title="Multi tenancy">Multi tenancy</a></li>
+ <li ><a href="sequences.html" title="Sequences">Sequences</a></li>
+ <li ><a href="array_type.html" title="ARRAY type">ARRAY type</a></li>
+ <li ><a href="salted.html" title="Salted Tables">Salted Tables</a></li>
+ <li ><a href="paged.html" title="Paged Queries">Paged Queries</a></li>
+ <li ><a href="dynamic_columns.html" title="Dynamic Columns">Dynamic Columns</a></li>
+ <li ><a href="skip_scan.html" title="Skip Scan">Skip Scan</a></li>
+ <li ><a href="bulk_dataload.html" title="Bulk Loading">Bulk Loading</a></li>
+ <li ><a href="tracing.html" title="Tracing">Tracing</a></li>
+ <li ><a href="update_statistics.html" title="Statistics Collection">Statistics Collection</a></li>
+ <li class="divider"/>
+ <li ><a href="phoenix_on_emr.html" title="Amazon EMR Support">Amazon EMR Support</a></li>
+ <li ><a href="flume.html" title="Apache Flume Plugin">Apache Flume Plugin</a></li>
+ <li ><a href="pig_integration.html" title="Apache Pig Integration">Apache Pig Integration</a></li>
+ </ul>
+ </li>
+ <li class="dropdown">
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown">Reference <b class="caret"></b></a>
+ <ul class="dropdown-menu">
+ <li ><a href="language/index.html" title="Grammar">Grammar</a></li>
+ <li ><a href="language/functions.html" title="Functions">Functions</a></li>
+ <li ><a href="language/datatypes.html" title="Datatypes">Datatypes</a></li>
+ </ul>
+ </li>
+ </ul>
+ </div><!--/.nav-collapse -->
+ </div>
+ </div>
+ </div>
+
+ <div class="container">
+
+ <!-- Masthead
+ ================================================== -->
+
+ <header>
+ </header>
+
+ <div class="main-body">
+ <div class="row">
+ <div class="span12">
+ <div class="body-content">
+<div class="page-header">
+ <h1>Upgrading Phoenix</h1>
+</div>
+<p>Phoenix uses a three number versioning schema of the form <major version>.<minor version>.<patch version>. For example, 4.2.1 has a major version of 4, a minor version of 2, and a patch version of 1.</p>
+<p>When upgrading to a new minor release (i.e. the major version is the same, but the minor version has changed), sometimes modifications to the system tables are necessary to either fix a bug or provide a new feature. This upgrade will occur automatically the first time a newly upgraded client connects to the newly upgraded server. It is expected that the server-side jar is upgraded first across your entire cluster, before any clients are upgraded. An older client will work with a newer server jar when the minor version is different, but not visa versa. In other words, clients do not need to be upgraded in lock step with the server. However, as of 4.2 and below, it is expected that all clients are upgraded at the same time (i.e. a mix of clients with different versions will not necessarily change). This may be improved in the future to allow a mix of old and new client versions (<a class="externalLink" href="https://issues.apache.org/jira/browse/PHOENIX-1483">PHOENIX-1483</a>)</p>
+<p>Upgrading to a new patch release may occur in any order: client first or server first, and a mix of clients with different patch release versions is fine.</p>
+<p>Upgrading to a new major release may require downtime as well as potentially the running of a migration script. This will be determined on a release by release basis.</p>
+<div class="section">
+ <h2 id="Upgrading_from_Phoenix_2.2.x_to_3.04.0">Upgrading from Phoenix 2.2.x to 3.0/4.0</h2>
+ <p>By default, Phoenix 2.2.x tables are not automatically upgraded to Apache Phoenix 3.0/4.0 tables. Since pre-Apache 2.2.x code lines have a different package structure (<tt>com.salesforce.phoenix</tt>) than the 3.0/4.0 code line (<tt>org.apache.phoenix</tt>), the two installations may actually coexist. An existing Phoenix table may either remain as a 2.2.x table or be upgraded to 3.0/4.0 table, but not both. In addition, a client JVM may either use the 3.0/4.0 driver or the 2.2.x driver, but not both. Upgrade, however, is a one way street: once a table is upgrade to 3.0/4.0, it stays that way.</p>
+ <p>Note that upgrading a table will not affect its data - only the metadata of the table will change. In order to upgrade tables from 2.2.x to 3.0/4.0, the following must be done <b>BEFORE</b> the first connection to a cluster which has 3.0/4.0 installed on it. </p>
+ <ul>
+ <li> <p>Add a new <tt>phoenix.client.autoUpgradeWhiteList</tt> config parameter to your client-side hbase-sites.xml. Make sure the directory containing the hbase-sites.xml is on the classpath of your client so that HBase finds it. The value you use for the parameter depends on which tables you want to upgrade:</p>
+ <ul>
+ <li>To upgrade all tables use a value of *. This will cause all Phoenix 2.2.x tables to be automatically converted to the new 3.0.0 structure when the first connection occurs. For example:</li>
+ </ul>
+ <div class="source">
+ <pre> <configuration>
+ <property>
+ <name>phoenix.client.autoUpgradeWhiteList</name>
+ <value>*</value>
+ </property>
+ </configuration>
+</pre>
+ </div>
+ <ul>
+ <li>To upgrade only some tables use a comma separated list of full table names. In that case, only those tables and their secondary indexes will be upgraded on first connection to a cluster. Note that table names are case sensitive. For example, the following would upgrade <tt>my_schema.my_table</tt> and <tt>MY_OTHER_TABLE</tt>:</li>
+ </ul>
+ <div class="source">
+ <pre> <configuration>
+ <property>
+ <name>phoenix.client.autoUpgradeWhiteList</name>
+ <value>my_schema.my_table,MY_OTHER_TABLE</value>
+ </property>
+ </configuration>
+</pre>
+ </div></li>
+ <li>After the first connection has been made to a cluster with Phoenix 3.0/4.0 installed, no further upgrade will take place. However, you may force it to take place again by removing the <tt>UpgradeTo30</tt> attribute from the <tt>SYSTEM.CATALOG</tt> HBase table metadata. Then, on the next connection to the cluster, upgrade will again occur as describe above.</li>
+ <li>If youâve been using a pre-release Phoenix 3.0/4.0 SNAPSHOT jar, your metadata wonât be compatible with the released metadata schema. You should disable and drop your SYSTEM.CATALOG and SYSTEM.SEQUENCE tables from an HBase shell and re-run your DDL commands to re-create your Phoenix table. In addition, make sure the SNAPSHOT jar is removed from your HBase lib directory and client directories.</li>
+ </ul>
+</div>
+ </div>
+ </div>
+ </div>
+ </div>
+
+ </div><!-- /container -->
+
+ <!-- Footer
+ ================================================== -->
+ <footer class="well">
+ <div class="container">
+ <div class="row">
+ <div class="span3 bottom-nav">
+ <ul class="nav nav-list">
+ <li class="nav-header">About</li>
+ <li >
+ <a href="index.html" title="Overview">Overview</a>
+ </li>
+ <li >
+ <a href="recent.html" title="New Features">New Features</a>
+ </li>
+ <li >
+ <a href="roadmap.html" title="Roadmap">Roadmap</a>
+ </li>
+ <li >
+ <a href="performance.html" title="Performance">Performance</a>
+ </li>
+ <li >
+ <a href="team.html" title="Team">Team</a>
+ </li>
+ <li >
+ <a href="contributing.html" title="Contributing">Contributing</a>
+ </li>
+ <li >
+ <a href="resources.html" title="Resources">Resources</a>
+ </li>
+ <li >
+ <a href="mailing_list.html" title="Mailing Lists">Mailing Lists</a>
+ </li>
+ <li >
+ <a href="source.html" title="Source Repository">Source Repository</a>
+ </li>
+ <li >
+ <a href="issues.html" title="Issue Tracking">Issue Tracking</a>
+ </li>
+ <li >
+ <a href="download.html" title="Download">Download</a>
+ </li>
+ <li >
+ <a href="http:divider" title=""></a>
+ </li>
+ <li >
+ <a href="release.html" title="How to release">How to release</a>
+ </li>
+ <li >
+ <a href="building_website.html" title="How to update website">How to update website</a>
+ </li>
+ <li >
+ <a href="http:divider" title=""></a>
+ </li>
+ <li >
+ <a href="http://www.apache.org/licenses/" title="License" class="externalLink">License</a>
+ </li>
+ <li >
+ <a href="http://www.apache.org/foundation/sponsorship.html" title="Sponsorship" class="externalLink">Sponsorship</a>
+ </li>
+ <li >
+ <a href="http://www.apache.org/foundation/thanks.html" title="Thanks" class="externalLink">Thanks</a>
+ </li>
+ <li >
+ <a href="http://www.apache.org/security/" title="Security" class="externalLink">Security</a>
+ </li>
+ </ul>
+ </div>
+ <div class="span3 bottom-nav">
+ <ul class="nav nav-list">
+ <li class="nav-header">Using</li>
+ <li >
+ <a href="faq.html" title="F.A.Q.">F.A.Q.</a>
+ </li>
+ <li >
+ <a href="Phoenix-in-15-minutes-or-less.html" title="Quick Start">Quick Start</a>
+ </li>
+ <li >
+ <a href="building.html" title="Building">Building</a>
+ </li>
+ <li >
+ <a href="tuning.html" title="Tuning">Tuning</a>
+ </li>
+ <li class="active">
+ <a href="#" title="Upgrading">Upgrading</a>
+ </li>
+ <li >
+ <a href="http:divider" title=""></a>
+ </li>
+ <li >
+ <a href="secondary_indexing.html" title="Secondary Indexes">Secondary Indexes</a>
+ </li>
+ <li >
+ <a href="joins.html" title="Joins">Joins</a>
+ </li>
+ <li >
+ <a href="subqueries.html" title="Subqueries">Subqueries</a>
+ </li>
+ <li >
+ <a href="views.html" title="Views">Views</a>
+ </li>
+ <li >
+ <a href="multi-tenancy.html" title="Multi tenancy">Multi tenancy</a>
+ </li>
+ <li >
+ <a href="sequences.html" title="Sequences">Sequences</a>
+ </li>
+ <li >
+ <a href="array_type.html" title="ARRAY type">ARRAY type</a>
+ </li>
+ <li >
+ <a href="salted.html" title="Salted Tables">Salted Tables</a>
+ </li>
+ <li >
+ <a href="paged.html" title="Paged Queries">Paged Queries</a>
+ </li>
+ <li >
+ <a href="dynamic_columns.html" title="Dynamic Columns">Dynamic Columns</a>
+ </li>
+ <li >
+ <a href="skip_scan.html" title="Skip Scan">Skip Scan</a>
+ </li>
+ <li >
+ <a href="bulk_dataload.html" title="Bulk Loading">Bulk Loading</a>
+ </li>
+ <li >
+ <a href="tracing.html" title="Tracing">Tracing</a>
+ </li>
+ <li >
+ <a href="update_statistics.html" title="Statistics Collection">Statistics Collection</a>
+ </li>
+ <li >
+ <a href="http:divider" title=""></a>
+ </li>
+ <li >
+ <a href="phoenix_on_emr.html" title="Amazon EMR Support">Amazon EMR Support</a>
+ </li>
+ <li >
+ <a href="flume.html" title="Apache Flume Plugin">Apache Flume Plugin</a>
+ </li>
+ <li >
+ <a href="pig_integration.html" title="Apache Pig Integration">Apache Pig Integration</a>
+ </li>
+ </ul>
+ </div>
+ <div class="span3 bottom-nav">
+ <ul class="nav nav-list">
+ <li class="nav-header">Reference</li>
+ <li >
+ <a href="language/index.html" title="Grammar">Grammar</a>
+ </li>
+ <li >
+ <a href="language/functions.html" title="Functions">Functions</a>
+ </li>
+ <li >
+ <a href="language/datatypes.html" title="Datatypes">Datatypes</a>
+ </li>
+ </ul>
+ </div>
+ <div class="span3 bottom-description">
+ <form action="http://search-hadoop.com/?" method="get"><input value="Phoenix" name="fc_project" type="hidden"><input placeholder="Search Phoenix…" required="required" style="width:170px;" size="18" name="q" id="query" type="search"></form>
+ </div>
+ </div>
+ </div>
+ </footer>
+
+ <div class="container subfooter">
+ <div class="row">
+ <div class="span12">
+ <p class="pull-right"><a href="#">Back to top</a></p>
+ <p class="copyright">Copyright ©2014 <a href="http://www.apache.org">Apache Software Foundation</a>. All Rights Reserved.</p>
+ </div>
+ </div>
+ </div>
+
+ <!-- Le javascript
+ ================================================== -->
+ <!-- Placed at the end of the document so the pages load faster -->
+ <script src="http://ajax.googleapis.com/ajax/libs/jquery/1.9.1/jquery.min.js"></script>
+
+ <script src="http://netdna.bootstrapcdn.com/twitter-bootstrap/2.3.2/js/bootstrap.min.js"></script>
+ <script src="./js/lightbox.js"></script>
+ <script src="./js/jquery.smooth-scroll.min.js"></script>
+ <!-- back button support for smooth scroll -->
+ <script src="./js/jquery.ba-bbq.min.js"></script>
+ <script src="http://yandex.st/highlightjs/7.5/highlight.min.js"></script>
+
+ <script src="./js/reflow-skin.js"></script>
+
+ </body>
+</html>
Modified: phoenix/site/publish/views.html
URL: http://svn.apache.org/viewvc/phoenix/site/publish/views.html?rev=1644823&r1=1644822&r2=1644823&view=diff
==============================================================================
--- phoenix/site/publish/views.html (original)
+++ phoenix/site/publish/views.html Fri Dec 12 04:07:50 2014
@@ -1,7 +1,7 @@
<!DOCTYPE html>
<!--
- Generated by Apache Maven Doxia at 2014-12-10
+ Generated by Apache Maven Doxia at 2014-12-11
Rendered using Reflow Maven Skin 1.1.0 (http://andriusvelykis.github.io/reflow-maven-skin)
-->
<html xml:lang="en" lang="en">
@@ -78,7 +78,7 @@
<li ><a href="Phoenix-in-15-minutes-or-less.html" title="Quick Start">Quick Start</a></li>
<li ><a href="building.html" title="Building">Building</a></li>
<li ><a href="tuning.html" title="Tuning">Tuning</a></li>
- <li ><a href="upgrade_from_2_2.html" title="Upgrade from 2.2">Upgrade from 2.2</a></li>
+ <li ><a href="upgrading.html" title="Upgrading">Upgrading</a></li>
<li class="divider"/>
<li ><a href="secondary_indexing.html" title="Secondary Indexes">Secondary Indexes</a></li>
<li ><a href="joins.html" title="Joins">Joins</a></li>
@@ -277,7 +277,7 @@ VALUES('John Doe', CURRENT_DATE(), NEXT
<a href="tuning.html" title="Tuning">Tuning</a>
</li>
<li >
- <a href="upgrade_from_2_2.html" title="Upgrade from 2.2">Upgrade from 2.2</a>
+ <a href="upgrading.html" title="Upgrading">Upgrading</a>
</li>
<li >
<a href="http:divider" title=""></a>
Modified: phoenix/site/source/src/site/markdown/news.md
URL: http://svn.apache.org/viewvc/phoenix/site/source/src/site/markdown/news.md?rev=1644823&r1=1644822&r2=1644823&view=diff
==============================================================================
--- phoenix/site/source/src/site/markdown/news.md (original)
+++ phoenix/site/source/src/site/markdown/news.md Fri Dec 12 04:07:50 2014
@@ -1,10 +1,8 @@
# Apache Phoenix News
<br/><hr/>
-### Phoenix 4.2.2, 3.2.2 released (Dec. 10, 2014)
-[Release Notes](https://raw.githubusercontent.com/apache/phoenix/4.2/CHANGES)
-
-Download the latest binary and source jars from [download page](download.html). Note Phoenix 4.x is compatible with HBase 0.98.1+ while Phoenix 3.x is compatible with HBase 0.94.x only.
-
+### Phoenix 4.2.2 [released](https://blogs.apache.org/phoenix/entry/announcing_phoenix_4_2_2)) (Dec. 10, 2014)
+For additional news, see our [blog](https://blogs.apache.org/phoenix/)
+Download the latest binary and source jars from [download page](download.html).
Modified: phoenix/site/source/src/site/markdown/resources.md
URL: http://svn.apache.org/viewvc/phoenix/site/source/src/site/markdown/resources.md?rev=1644823&r1=1644822&r2=1644823&view=diff
==============================================================================
--- phoenix/site/source/src/site/markdown/resources.md (original)
+++ phoenix/site/source/src/site/markdown/resources.md Fri Dec 12 04:07:50 2014
@@ -1,5 +1,5 @@
#Resources
-Below are some prior presentations that have been done on Apache Phoenix.
+Below are some prior presentations that have been done on Apache Phoenix. Another good source of information is the Apache Phoenix [blog](https://blogs.apache.org/phoenix/).
| Conference | Video | Presentation |
|------------|-------|--------------|
Added: phoenix/site/source/src/site/markdown/upgrading.md
URL: http://svn.apache.org/viewvc/phoenix/site/source/src/site/markdown/upgrading.md?rev=1644823&view=auto
==============================================================================
--- phoenix/site/source/src/site/markdown/upgrading.md (added)
+++ phoenix/site/source/src/site/markdown/upgrading.md Fri Dec 12 04:07:50 2014
@@ -0,0 +1,35 @@
+#Upgrading Phoenix
+
+Phoenix uses a three number versioning schema of the form <major version>.<minor version>.<patch version>. For example, 4.2.1 has a major version of 4, a minor version of 2, and a patch version of 1.
+
+When upgrading to a new minor release (i.e. the major version is the same, but the minor version has changed), sometimes modifications to the system tables are necessary to either fix a bug or provide a new feature. This upgrade will occur automatically the first time a newly upgraded client connects to the newly upgraded server. It is expected that the server-side jar is upgraded first across your entire cluster, before any clients are upgraded. An older client will work with a newer server jar when the minor version is different, but not visa versa. In other words, clients do not need to be upgraded in lock step with the server. However, as of 4.2 and below, it is expected that all clients are upgraded at the same time (i.e. a mix of clients with different versions will not necessarily change). This may be improved in the future to allow a mix of old and new client versions ([PHOENIX-1483](https://issues.apache.org/jira/browse/PHOENIX-1483))
+
+Upgrading to a new patch release may occur in any order: client first or server first, and a mix of clients with different patch release versions is fine.
+
+Upgrading to a new major release may require downtime as well as potentially the running of a migration script. This will be determined on a release by release basis.
+
+##Upgrading from Phoenix 2.2.x to 3.0/4.0
+
+By default, Phoenix 2.2.x tables are not automatically upgraded to Apache Phoenix 3.0/4.0 tables. Since pre-Apache 2.2.x code lines have a different package structure (<code>com.salesforce.phoenix</code>) than the 3.0/4.0 code line (<code>org.apache.phoenix</code>), the two installations may actually coexist. An existing Phoenix table may either remain as a 2.2.x table or be upgraded to 3.0/4.0 table, but not both. In addition, a client JVM may either use the 3.0/4.0 driver or the 2.2.x driver, but not both. Upgrade, however, is a one way street: once a table is upgrade to 3.0/4.0, it stays that way.
+
+Note that upgrading a table will not affect its data - only the metadata of the table will change. In order to upgrade tables from 2.2.x to 3.0/4.0, the following must be done **BEFORE** the first connection to a cluster which has 3.0/4.0 installed on it.
+
+* Add a new <code>phoenix.client.autoUpgradeWhiteList</code> config parameter to your client-side hbase-sites.xml. Make sure the directory containing the hbase-sites.xml is on the classpath of your client so that HBase finds it. The value you use for the parameter depends on which tables you want to upgrade:
+ * To upgrade all tables use a value of *. This will cause all Phoenix 2.2.x tables to be automatically converted to the new 3.0.0 structure when the first connection occurs. For example:
+
+ <configuration>
+ <property>
+ <name>phoenix.client.autoUpgradeWhiteList</name>
+ <value>*</value>
+ </property>
+ </configuration>
+ * To upgrade only some tables use a comma separated list of full table names. In that case, only those tables and their secondary indexes will be upgraded on first connection to a cluster. Note that table names are case sensitive. For example, the following would upgrade <code>my_schema.my_table</code> and <code>MY_OTHER_TABLE</code>:
+
+ <configuration>
+ <property>
+ <name>phoenix.client.autoUpgradeWhiteList</name>
+ <value>my_schema.my_table,MY_OTHER_TABLE</value>
+ </property>
+ </configuration>
+* After the first connection has been made to a cluster with Phoenix 3.0/4.0 installed, no further upgrade will take place. However, you may force it to take place again by removing the <code>UpgradeTo30</code> attribute from the <code>SYSTEM.CATALOG</code> HBase table metadata. Then, on the next connection to the cluster, upgrade will again occur as describe above.
+* If you've been using a pre-release Phoenix 3.0/4.0 SNAPSHOT jar, your metadata won't be compatible with the released metadata schema. You should disable and drop your SYSTEM.CATALOG and SYSTEM.SEQUENCE tables from an HBase shell and re-run your DDL commands to re-create your Phoenix table. In addition, make sure the SNAPSHOT jar is removed from your HBase lib directory and client directories.
Modified: phoenix/site/source/src/site/site.xml
URL: http://svn.apache.org/viewvc/phoenix/site/source/src/site/site.xml?rev=1644823&r1=1644822&r2=1644823&view=diff
==============================================================================
--- phoenix/site/source/src/site/site.xml (original)
+++ phoenix/site/source/src/site/site.xml Fri Dec 12 04:07:50 2014
@@ -79,7 +79,7 @@
<item href="Phoenix-in-15-minutes-or-less.html" name="Quick Start"/>
<item href="building.html" name="Building"/>
<item href="tuning.html" name="Tuning"/>
- <item href="upgrade_from_2_2.html" name="Upgrade from 2.2"/>
+ <item href="upgrading.html" name="Upgrading"/>
<item href="http:divider" name=""/>
<item href="secondary_indexing.html" name="Secondary Indexes"/>
<item href="joins.html" name="Joins"/>