accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sean Busbey <>
Subject Re: [DISCUSS] Establishing a contrib repo for upgrade testing
Date Fri, 06 Mar 2015 16:04:08 GMT
I was asked off-list why I think this should be in a contrib.

My primary reasons are

1) I want our upgrade code to be versioned independently, because it will
necessarily need to work across versions.

That is, I want a single tool that can be used to test both 1.5.2 -> 1.6.0,
1.6.1 -> 1.6.3, 1.6.z -> 1.7.0, 1.5.2 -> 1.7.0 etc.

This is one area where the current tools need some work, because I dealt
with API changes by just tagging different Accumulo-compatible versions.

2) I want to use a released artifact to test candidate releases of the main

I'd like us to be aware of what changes, if any, had to go into our upgrade
testing code to test our new candidate releases. That issue is muddled when
those changes are tied up in the candidate under consideration.

3) I want a downstream project that we (the PMC) have a direct stake in
that will give us better awareness of when our changes cause clients to
alter behavior.

Right now, the only time things like ACCUMULO-3402 show up is when someone
goes to integrate with another ecosystem component. Having a project
"closer to home" makes it easier for these things to come up before we do a

On Fri, Mar 6, 2015 at 9:15 AM, Sean Busbey <> wrote:

> Hi Accumulo!
> Cloudera has recently made public some code used for doing correctness
> testing for Accumulo installations across upgrades[1]. The project contains
> simple data load and verification tools as well as a rudimentary upgrade
> test automation script.
> We would like to donate this code to the ASF and use it as a starting
> place for a contrib repository focused on testing Accumulo across versions
> generally. If the PMC is interested, I'd be happy to take point on the
> necessary paperwork for IP clearance[2] following an appropriate vote.
> Though simple, this upgrade testing has already found issues around 1.4 ->
> 1.5 -> 1.6 and 1.4 ->1.6 upgrades in the past. There are some obvious
> points of clean up that need to happen (vendor specific references in docs,
> artifacts, and packages), and I'd be happy to take point on that work as
> well. I think it would make a good foundational layer for our future needs
> and would give us a place where we could revitalize the work from
> ACCUMULO-2145.
> Thoughts?
> [1]:
> [2]:
> --
> Sean


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message