Proposal: Should we remove hadoop 1.0 build support in future major release

[Jeffrey Zhong <jz...@hortonworks.com>]

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.

Re: Proposal: Should we remove hadoop 1.0 build support in future major release

[Andrew Purtell <ap...@apache.org>]

+1

I think this is the right direction since we'd like to drop Hadoop 1
support upstream from you in HBase at some point, hopefully sooner than
later.


On Fri, Feb 28, 2014 at 10:40 AM, Jeffrey Zhong <jz...@hortonworks.com>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.
>



-- 
Best regards,

   - Andy

Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)

Re: Proposal: Should we remove hadoop 1.0 build support in future major release

[James Taylor <ja...@apache.org>]

Let's just ping Lars too, as I don't want to get in a bind if we need h1
around for example to allow folks to migrate from Phoenix 2.2 directly to
Phoenix 4.0.

What do you think, Lars?


On Fri, Feb 28, 2014 at 5:14 PM, Enis Söztutar <en...@gmail.com> wrote:

> 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 <jamestaylor@apache.org
> >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 <
> > ramkrishna.s.vasudevan@intel.com> wrote:
> >
> > > +1 on dropping
> > >
> > > -----Original Message-----
> > > From: Anoop John [mailto:anoop.hbase@gmail.com]
> > > Sent: Friday, February 28, 2014 9:08 AM
> > > To: dev@phoenix.incubator.apache.org
> > > 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 <en...@gmail.com>
> > 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 <
> jzhong@hortonworks.com
> > > > >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.
> > > > >
> > > >
> > >
> >
>

Re: Proposal: Should we remove hadoop 1.0 build support in future major release

[Enis Söztutar <en...@gmail.com>]

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 <ja...@apache.org>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 <
> ramkrishna.s.vasudevan@intel.com> wrote:
>
> > +1 on dropping
> >
> > -----Original Message-----
> > From: Anoop John [mailto:anoop.hbase@gmail.com]
> > Sent: Friday, February 28, 2014 9:08 AM
> > To: dev@phoenix.incubator.apache.org
> > 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 <en...@gmail.com>
> 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 <jzhong@hortonworks.com
> > > >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.
> > > >
> > >
> >
>

Re: Proposal: Should we remove hadoop 1.0 build support in future major release

[James Taylor <ja...@apache.org>]

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 <
ramkrishna.s.vasudevan@intel.com> wrote:

> +1 on dropping
>
> -----Original Message-----
> From: Anoop John [mailto:anoop.hbase@gmail.com]
> Sent: Friday, February 28, 2014 9:08 AM
> To: dev@phoenix.incubator.apache.org
> 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 <en...@gmail.com> 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 <jzhong@hortonworks.com
> > >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.
> > >
> >
>

RE: Proposal: Should we remove hadoop 1.0 build support in future major release

["Vasudevan, Ramkrishna S" <ra...@intel.com>]

+1 on dropping

-----Original Message-----
From: Anoop John [mailto:anoop.hbase@gmail.com] 
Sent: Friday, February 28, 2014 9:08 AM
To: dev@phoenix.incubator.apache.org
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 <en...@gmail.com> 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 <jzhong@hortonworks.com
> >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.
> >
>

Re: Proposal: Should we remove hadoop 1.0 build support in future major release

[Anoop John <an...@gmail.com>]

> 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 <en...@gmail.com> 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 <jzhong@hortonworks.com
> >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.
> >
>

Re: Proposal: Should we remove hadoop 1.0 build support in future major release

[Enis Söztutar <en...@gmail.com>]

+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 <jz...@hortonworks.com>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.
>