You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by Sean Busbey <bu...@apache.org> on 2018/02/27 15:42:23 UTC
[DISCUSS] dropping hadoop 2 support
Let's get the discussion started early on when we'll drop hadoop 2 support.
As of ACCUMULO-4826 we are poised to have Hadoop 2 and Hadoop 3 supported in 1.y releases as of 1.9.0. That gives an upgrade path so that folks won't have to upgrade both Hadoop and Accumulo at the same time.
How about Accumulo 2.0.0 requires Hadoop 3?
If there's a compelling reason for our users to stay on Hadoop 2.y releases, we can keep making Accumulo 1.y releases. Due to the shift away from maintenance releases in Hadoop we'll need to get more aggressive in adopting minor releases.
Re: [DISCUSS] dropping hadoop 2 support
Posted by Josh Elser <el...@apache.org>.
+1
AFAIK, this wouldn't have to be anything more than build changes.
"Dropping hadoop2 support" wouldn't need to include any other changes
(as adding H3 support didn't require any Java changes). Getting in front
of the ball to help push people towards newer versions would be a
welcome change.
On 2/27/18 10:42 AM, Sean Busbey wrote:
> Let's get the discussion started early on when we'll drop hadoop 2 support.
>
> As of ACCUMULO-4826 we are poised to have Hadoop 2 and Hadoop 3 supported in 1.y releases as of 1.9.0. That gives an upgrade path so that folks won't have to upgrade both Hadoop and Accumulo at the same time.
>
> How about Accumulo 2.0.0 requires Hadoop 3?
>
> If there's a compelling reason for our users to stay on Hadoop 2.y releases, we can keep making Accumulo 1.y releases. Due to the shift away from maintenance releases in Hadoop we'll need to get more aggressive in adopting minor releases.
>
Re: [DISCUSS] dropping hadoop 2 support
Posted by Christopher <ct...@apache.org>.
It seems there's consensus on this, so I'll start moving forward on this
soon.
On Tue, Feb 27, 2018 at 12:40 PM Keith Turner <ke...@deenlo.com> wrote:
> +1
>
> On Tue, Feb 27, 2018 at 10:42 AM, Sean Busbey <bu...@apache.org> wrote:
> > Let's get the discussion started early on when we'll drop hadoop 2
> support.
> >
> > As of ACCUMULO-4826 we are poised to have Hadoop 2 and Hadoop 3
> supported in 1.y releases as of 1.9.0. That gives an upgrade path so that
> folks won't have to upgrade both Hadoop and Accumulo at the same time.
> >
> > How about Accumulo 2.0.0 requires Hadoop 3?
> >
> > If there's a compelling reason for our users to stay on Hadoop 2.y
> releases, we can keep making Accumulo 1.y releases. Due to the shift away
> from maintenance releases in Hadoop we'll need to get more aggressive in
> adopting minor releases.
>
Re: [DISCUSS] dropping hadoop 2 support
Posted by Keith Turner <ke...@deenlo.com>.
+1
On Tue, Feb 27, 2018 at 10:42 AM, Sean Busbey <bu...@apache.org> wrote:
> Let's get the discussion started early on when we'll drop hadoop 2 support.
>
> As of ACCUMULO-4826 we are poised to have Hadoop 2 and Hadoop 3 supported in 1.y releases as of 1.9.0. That gives an upgrade path so that folks won't have to upgrade both Hadoop and Accumulo at the same time.
>
> How about Accumulo 2.0.0 requires Hadoop 3?
>
> If there's a compelling reason for our users to stay on Hadoop 2.y releases, we can keep making Accumulo 1.y releases. Due to the shift away from maintenance releases in Hadoop we'll need to get more aggressive in adopting minor releases.
Re: [DISCUSS] dropping hadoop 2 support
Posted by Christopher <ct...@apache.org>.
+1 I'm in favor of this.
On Tue, Feb 27, 2018 at 10:42 AM Sean Busbey <bu...@apache.org> wrote:
> Let's get the discussion started early on when we'll drop hadoop 2 support.
>
> As of ACCUMULO-4826 we are poised to have Hadoop 2 and Hadoop 3 supported
> in 1.y releases as of 1.9.0. That gives an upgrade path so that folks won't
> have to upgrade both Hadoop and Accumulo at the same time.
>
> How about Accumulo 2.0.0 requires Hadoop 3?
>
> If there's a compelling reason for our users to stay on Hadoop 2.y
> releases, we can keep making Accumulo 1.y releases. Due to the shift away
> from maintenance releases in Hadoop we'll need to get more aggressive in
> adopting minor releases.
>