Since 3.0 targets 0.94, it makes sense to keep h1, and h2 compat.

Let's drop it in 4.0 then if it makes your life easier Jeffrey.
Enis


On Fri, Feb 28, 2014 at 11:24 AM, James Taylor <[email protected]>wrote:

> I'm +1 on dropping Hadoop 1 for 4.0 and above. I think we should keep it
> for our 3.0 release, though.
>
>
> On Thu, Feb 27, 2014 at 7:53 PM, Vasudevan, Ramkrishna S <
> [email protected]> wrote:
>
> > +1 on dropping
> >
> > -----Original Message-----
> > From: Anoop John [mailto:[email protected]]
> > Sent: Friday, February 28, 2014 9:08 AM
> > To: [email protected]
> > Subject: Re: Proposal: Should we remove hadoop 1.0 build support in
> future
> > major release
> >
> > > It doesn't directly use
> > hadoop. The places it depends on hadoop one or two is in test code like
> > using HBaseMiniCluster.
> >
> > +1 on dropping.
> >
> > -Anoop-
> >
> > On Fri, Feb 28, 2014 at 8:11 AM, Enis Söztutar <[email protected]>
> wrote:
> >
> > > +1 on dropping support for hadoop1 in Phoenix.
> > >
> > > I think HBase might still have some support for Hadoop 1 for legacy
> > > reasons, Phoenix is not burdened by that.
> > >
> > > Enis
> > >
> > >
> > > On Thu, Feb 27, 2014 at 6:40 PM, Jeffrey Zhong <[email protected]
> > > >wrote:
> > >
> > > > Hey,
> > > >
> > > > Phoenix is an application built on top of hbase. It doesn't directly
> > > > use hadoop. The places it depends on hadoop one or two is in test
> > > > code like using HBaseMiniCluster. While during run time, Phoenix
> > > > built with hadoop1 should work with a live hbase cluster running on
> > hadoop2 and vice verse.
> > > > In addition, latest Hbase is now built on hadoop2 by default.
> > > >
> > > > Just a thought when I was looking at pom today. If we can remove the
> > > > hadoop1.0 from build, we can clean our code structure and pom quite
> > > > a
> > > bit.
> > > >
> > > > Thanks,
> > > > -Jeffrey
> > > >
> > > >
> > > >
> > > > --
> > > > CONFIDENTIALITY NOTICE
> > > > NOTICE: This message is intended for the use of the individual or
> > > > entity
> > > to
> > > > which it is addressed and may contain information that is
> > > > confidential, privileged and exempt from disclosure under applicable
> > > > law. If the reader of this message is not the intended recipient,
> > > > you are hereby notified
> > > that
> > > > any printing, copying, dissemination, distribution, disclosure or
> > > > forwarding of this communication is strictly prohibited. If you have
> > > > received this communication in error, please contact the sender
> > > immediately
> > > > and delete it from your system. Thank You.
> > > >
> > >
> >
>

Reply via email to