phoenix-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Josh Elser <josh.el...@gmail.com>
Subject Re: Phoenix Upgrade compatibility
Date Tue, 20 Jun 2017 18:55:30 GMT
Yes, vendors are as vendors do.

Requests for new versions of Phoenix should go to those channels. The 
Apache community has no control over what versions vendors ship.

On 6/16/17 8:08 PM, Michael Young wrote:
> Updating my question here:
> 
> I found some info from a post on May 19th under (Upgrade Phoenix version 
> on HDP 2.4).
> 
> It seems for those using HDP 2.6, we are stuck with Phoenix 4.7 until 
> the next Hortonworks release. :(
> 
> To any Hortonworks people out there: Is there any way we could do a full 
> install of Phoenix 4.10 (essentially from scratch, not a rolling upgrade 
> or just replacing the jars), and get it to work in HDP 2.6?  I would 
> think so, but we don't want to live too much on the edge, just enough to 
> not wait too long. :)
> 
> Michael
> 
> 
> On Fri, Jun 16, 2017 at 5:01 PM, Michael Young <yomaiquin@gmail.com 
> <mailto:yomaiquin@gmail.com>> wrote:
> 
>     According to https://phoenix.apache.org/upgrading.html
>     <https://phoenix.apache.org/upgrading.html>
> 
>     "Phoenix maintains backward compatibility across at least two minor
>     releases to allow for *no downtime* through server-side rolling
>     restarts upon upgrading. See below for details"
> 
>     We would like to upgrade from version 4.7 to a newer version.
> 
>     Any recommendations on which version we should get (latest?) and if
>     we should do an incremental upgrade or move directly to the latest 4.10?
> 
>     Thanks,
>     Michael
> 
> 

Mime
View raw message