phoenix-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Taylor <jamestay...@apache.org>
Subject Re: Version compatibility policy
Date Fri, 24 Jun 2016 11:26:54 GMT
James,

We support upgrading among minor versions with no downtime (at least two
versions back, but in reality we go back further than that currently). See
our backward compatibility documentation here:
http://phoenix.apache.org/upgrading.html.

For 4.8, we've made some changes to local indexing and indexes on views
that require them to be rebuilt once you've deployed 4.8 on your cluster.
This is a bit out of the norm. We won't make changes to our data model that
would require any kind of downtime, though to take advantage of some new
features, you'd need to create a new table (for example with the new column
encoding features under development).

The EMR group at Amazon seem open to upgrading to new versions of Phoenix,
though I can't of course speak on their behalf.

Thanks,
James

On Fri, Jun 24, 2016 at 12:38 PM, Heather, James (ELS) <
james.heather@elsevier.com> wrote:

> Is there a clear policy for version compatibility for Phoenix? If I create
> and populate tables using Phoenix 4.7, is it certain that there will be a
> non-disruptive upgrade path to 4.8, 4.9, 5.0...?
>
> Also, is there any indication from Amazon about support for future
> versions? Will they provide an upgrade path?
>
> James
>
> ------------------------------
>
> Elsevier Limited. Registered Office: The Boulevard, Langford Lane,
> Kidlington, Oxford, OX5 1GB, United Kingdom, Registration No. 1982084,
> Registered in England and Wales.
>

Mime
View raw message