accumulo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher <>
Subject Re: [DISCUSS] Should we support upgrading 1.4 -> 1.6 w/o going through 1.5?
Date Wed, 18 Jun 2014 17:56:50 GMT
My main concern would be the risk of destabilizing 1.6.x by reintroducing
upgrade code to support upgrading from both 1.4.x and 1.5.x. So long as
that risk is mitigated by making the changeset minimal and thorough
review/testing, I see no issue with providing a direct upgrade path from
1.4.x/1.5.x -> 1.6.1. I wouldn't want to make it a precedent, though. It's
hard enough supporting upgrades from one prior version.

Christopher L Tubbs II

On Mon, Jun 16, 2014 at 5:24 PM, Sean Busbey <> wrote:

> In an effort to get more users off of our now unsupported 1.4 release,
> should we support upgrading directly to 1.6 without going through a 1.5
> upgrade?
> More directly for those on user@: would you be more likely to upgrade off
> of 1.4 if you could do so directly to 1.6?
> We have this working locally at Cloudera as a part of our CDH integration
> (we shipped 1.4 and we're planning to ship 1.6 next).
> We can get into implementation details on a jira if there's positive
> consensus, but the changes weren't very complicated. They're mostly
> * forward porting and consolidating some upgrade code
> * additions to the README for instructions
> Personally, I can see the both sides of the argument. On the plus side,
> anything to get more users off of 1.4 is a good thing. On the negative
> side, it means we have the 1.4 related upgrade code sitting in a supported
> code branch longer.
> Thoughts?
> --
> Sean

View raw message