accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Josh Elser <>
Subject Re: [DISCUSS] Htrace4, Hadoop 2.7
Date Fri, 08 Jul 2016 21:15:56 GMT
Sean Busbey wrote:
> On Fri, Jul 8, 2016 at 3:40 PM, Christopher<>  wrote:
>> On Fri, Jul 8, 2016 at 11:20 AM Sean Busbey<>  wrote:
>>> Would we be bumping the Hadoop version while incrementing our minor
>>> version number or our major version number?
>> Minor only, because it's not a breaking change necessarily, and it's
>> unrelated to API. It'd still be reasonable for somebody to patch the 1.x
>> version to use the earlier Hadoop/HTrace versions easily.
>> Specifically, I was thinking for 1.8.0. Since H2.8 isn't out yet, that'd
>> mean either no change in 1.8.0, or a change to make it sync up with H2.7.
> My only concern would be that updating our listed Hadoop dependency
> version would make it easy for someone to accidentally rely on a
> Hadoop API call that wasn't in earlier versions, which would then make
> it harder for an interested person to patch their 1.y version to use
> the earlier Hadoop version.
> HBase checks compilation against different hadoop versions in their
> precommit checks. We could add something like that to our nightly
> builds maybe?
> Now that we're discussing it, I can't actually remember if we ever
> documented what version(s) of Hadoop we expect to work with. So maybe
> updating to the latest minor release of 2.y on each Accumulo 1.y minor
> release can just be our new thing.

It was 2.2.0 for the longest time. I feel like we switched it to 
2.6.something when we ran into some issues with UGI+Kerberos.

1.8.0 seems to be good timing for this (as is likely Christopher's 
reason for bringing it up now).

View raw message