hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sean Busbey <bus...@apache.org>
Subject Re: [DISCUSS] Changing hadoop check versions in our hbase-personality?
Date Tue, 23 Oct 2018 01:09:31 GMT
Zach you fine with conversation about this on the JIRA or you wanna do on
the list?

On Mon, Oct 22, 2018, 19:51 Zach York <zyork.contribution@gmail.com> wrote:

> What is the main reason for the change? Build time speedup?
>
> Any reason for testing all of the 2.6.x line, but not the 2.7.x line? We
> don't check at all for 2.8.x?
>
> Can we be more consistent with how we test compatibility? (Do we only care
> about the latest patch release in a line?)
>
> Sorry If I'm missing some of the reasoning, but at a surface level it seems
> fairly arbitrary which releases we are cutting.
>
> On Mon, Oct 22, 2018 at 5:44 PM Sean Busbey <busbey@apache.org> wrote:
>
> > Please leave me time to review before it is committed.
> >
> > On Mon, Oct 22, 2018, 13:58 Stack <stack@duboce.net> wrote:
> >
> > > Duo has a patch up on HBASE-20970 that changes the Hadoop versions we
> > check
> > > at build time. Any objections to committing to branch-2.1+?
> > >
> > > It makes following changes:
> > >
> > > 2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 2.7.4
> > >
> > > becomes
> > >
> > > 2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.7
> > >
> > > And...
> > >
> > > 3.0.0
> > >
> > > goes to
> > >
> > > 3.0.3
> > >
> > > Shout if you are against the change else will commit tomorrow.
> > >
> > > Thanks,
> > > S
> > >
> >
>

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