What version of Phoenix 4 are you coming from?
Of note, if you're lagging far behind, you'll get bit by the column
encoding turning on by default in 4.10 [1]
In general, before we update the system catalog table, we take a
snapshot of it, so you can roll back (although this would be manual). In
terms of testing as a community, we only do testing back two releases.
After that, your mileage may vary.
- Josh
[1] https://phoenix.apache.org/columnencoding.html
On 6/11/19 9:02 PM, Vova Galchenko wrote:
Hello Phoenix Users List!
We at Box are thinking about the upgrade story from Phoenix 4 to 5. As
part of that, we'd like to understand if these Phoenix versions write
data in formats compatible with each other. In other words, suppose we
have an HBase 1.4 cluster used by Phoenix 4. Can I shut everything down,
upgrade HBase to 2.0 and Phoenix to 5, start everything up again, and
expect to preserve the integrity of the data stored in the original
cluster? If not, is there guidance for what the upgrade process might
look like?
Thanks,
vova
