[PHOENIX-99] Automatic white list based upgrade from 2.2 to 3.0

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0
• Fix Version/s: 3.0.0
• Assignee: James R. Taylor
• Reporter: James R. Taylor
• Created: 03/Mar/14 09:17
• Updated: 21/Nov/15 02:16
• Resolved: 04/Mar/14 09:25

Description

Auto upgrade tables from Phoenix 2.2.2/2.2.3 format to Phoenix 3.0 format. Note that upgrade is only attempted to be performed once, upon first connection to a cluster. A table is only upgraded if it is white listed based on the following new config property: phoenix.client.autoUpgradeWhiteList

If this property is not present, no tables will be upgraded. The config property may have the following values:

• * which means upgrade everything or
• a comma separated list of fully qualified, case sensitive names (note that by default, Phoenix stores table names in uppercase unless put them in double quotes at DDL time)

Examples:

  <property>
    <name>phoenix.client.autoUpgradeWhiteList</name>
    <value>*</value> <!- will upgrade all tables ->
  </property>

  <property>
    <name>phoenix.client.autoUpgradeWhiteList</name>
    <value>MY_SCHEMA.MY_TABLE, OTHER_TABLE</value>
  </property>

The upgrade is only run once per connection to a cluster (when the SYSTEM.CATALOG is created). If you need to force it to run again after that, you can remove or set to "false" the UpgradeTo30 value that's stored in the metadata of the SYSTEM.CATALOG table.