We'll definitely remove hadoop1 support from 4.x, as it's causing pom issues. We can't support both hadoop1 and hadoop2 and make hadoop2 the default (see prior discussions - basically due to how other projects poms are authored).
Sounds like a few folks are still relying on hadoop1 for 3.x, so I guess we can leave support there a while longer. Thanks, James On Tue, Sep 23, 2014 at 10:54 AM, lars hofhansl <la...@apache.org> wrote: > At the very least we could make hadoop2 the default target in 4.x. > Seems fair to remove all the cruft from the 4 branch, too. > > There's still a fair amount of usage of HBase 0.94 on top of Hadoop 1. > So maybe keep it alive in 3.0? 3.0 can be retired when HBase 0.94 is retired > (although I have no plans for 0.94 retirement, yet). > > -- Lars > > > ----- Original Message ----- > From: James Taylor <jamestay...@apache.org> > To: "d...@phoenix.apache.org" <d...@phoenix.apache.org>; user > <user@phoenix.apache.org> > Cc: > Sent: Monday, September 22, 2014 10:19 PM > Subject: anyone relying on hadoop1 still? > > Hello, > We've been planning on dropping hadoop1 support for our 4.x releases > for a while now and it looks like it'll happen in 4.2. It'd be nice if > we could do the same for our 3.x releases, as the more similar the two > branches are, the less time it takes to keep them in sync. > > Is anyone out there still relying on hadoop1 support for future 3.x releases? > > Thanks, > James >