[
https://issues.apache.org/jira/browse/PHOENIX-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13943741#comment-13943741
]
James Taylor commented on PHOENIX-884:
--------------------------------------
We just put out another RC here:
http://mail-archives.apache.org/mod_mbox/incubator-phoenix-dev/201403.mbox/%3CCAAF1JdiBkqtR9FkEow-kGd1xsxZ%2B0B1-7NejH%3Duygocx_iM30g%40mail.gmail.com%3E
If you use that one, you can migrate pretty easily by doing the following:
- *BEFORE* you make any connection to a cluster with Phoenix 3.0.0 installed,
add a phoenix.client.autoUpgradeWhiteList parameter to your client-side
hbase-sites.xml with a value of *. This will cause all Phoenix 2.2.x tables to
be automatically converted to the new 3.0.0 structure. Make sure the directory
containing the hbase-sites.xml is on the classpath of your client. For example:
{code}
<configuration>
<property>
<name>phoenix.client.autoUpgradeWhiteList</name>
<value>*</value>
</property>
</configuration>
{code}
- When you make the first connection through Phoenix, all your tables will be
upgraded. No table data is being rewritten, it's only the metadata that is
changing.
I'll write this up on a wiki soon, but I wanted to give you this information
because it sounds like you're in a hurry.
> How to migrate from 2.2.0 to 3.0.0
> ----------------------------------
>
> Key: PHOENIX-884
> URL: https://issues.apache.org/jira/browse/PHOENIX-884
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: yang ming
> Priority: Critical
>
> In my cluster there are many tables created by 2.2.0,but when doing system
> upgrade I find the package structure of version 3.0.0 has been changed,so how
> to migrate from 2.2.0 to 3.0.0?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
