[
https://issues.apache.org/jira/browse/PHOENIX-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13943900#comment-13943900
]
Lars Hofhansl edited comment on PHOENIX-884 at 3/22/14 4:31 AM:
----------------------------------------------------------------
As a general comment (and I am speaking from the viewpoint of an HBase
committer not for Phoenix as such) you should *never* deploy not-released or RC
code in a production setting. There will be an upgrade path from
official-version-X to official-version-Y, but not from version-3/31/14 or
version-X-RC to official-version-Y. As James mentioned things may change and
are only really stable at the official versions. (although an RC is probably
safe)
If you do that anyway you'll likely be on your own.
>From the viewpoint of a mentor to this project I would also say that we should
>be very clear that it might work, but is entirely not supported and things
>might change in a way that renders all existing data useless for the next
>official version (and/or will need hackery that you yourself have to do to fix
>up your data).
Sorry for the bit of the rant here, but unreleased software and RCs are *not*
meant for production.
was (Author: lhofhansl):
As a general comment (and I am speaking from the viewpoint of an HBase
committer not for Phoenix as such) you should *never* deploy not-released or RC
code in a production setting. There will be an upgrade path from
official-version-X to official-version-Y, but not from version-3/31/14 or
version-X-RC to official-version-Y. As James mentioned things may change and
are only really stable at the official versions. (although an RC is probably
safe)
If you do that anyway you'll likely be on your own.
>From the viewpoint of a mentor to this project I would also say that we should
>be very clear that it might work, but is entirely not supported and things
>might change in a way the render all existing data useless for the next
>official version (and/or will need hackery that you yourself have to do to fix
>up your data).
Sorry for the bit of the rant here, but unreleased software and RCs are *not*
meant for production.
> 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)
