Thanks for the explanation, Thejas. I was just wondering how come we're
suddenly making a decision out of nowhere. It might be rare, but I do know
users being still on 0.20. Regardless, I think a long term plan for things
like this would be helpful to avoid surprises. I know we discussed about
this in the past, but it never reached a consensus. Maybe we should have
had a vote like this at that time.

Having said that, I understand value of the dev savings. So, go ahead.

On the side note, the next thing to drop might be JDK6. Maybe we can start
voting on a plan on that in advance.

--Xuefu

On Tue, Oct 7, 2014 at 7:48 PM, Thejas Nair <the...@hortonworks.com> wrote:

> Xuefu,
>
> I am working on a patch that requires adding shims (HIVE-8384). It is
> just that the changes are uglier than they need to be, because of
> hadoop 0.20 . It does not support objects such as Tokens. I have been
> thinking of starting this thread of a while, and it took this patch
> for me to overcome my laziness. Better late than never!
>
> We are not upgrading the installs on user environments automatically.
> Communicating this at beginging of the release would give them
> additional 3 months or so of notice. I don't think that matters a lot.
> As I mentioned earlier, I really doubt if people on hadoop 0.20  (if
> any) are going to upgrade to newer versions of hive. The added dev
> burden is unwarranted.
>
>
> On Tue, Oct 7, 2014 at 6:54 PM, Xuefu Zhang <xzh...@cloudera.com> wrote:
> > I'd like to understand the motivation a bit. I'm okay to drop the
> support,
> > but given a release that's pending, sudden move seems rather rushy, given
> > user no time to react. It might be more considerate to communicate it at
> > the beginning of the release cycle rather than a few days before the
> > release.
> >
> > On Tue, Oct 7, 2014 at 6:02 PM, Edward Capriolo <edlinuxg...@gmail.com>
> > wrote:
> >
> >> +1
> >>
> >> On Tue, Oct 7, 2014 at 7:51 PM, Vikram Dixit <vik...@hortonworks.com>
> >> wrote:
> >>
> >> > +1
> >> >
> >> > On Tue, Oct 7, 2014 at 4:44 PM, Bill Busch <bill.bu...@perficient.com
> >
> >> > wrote:
> >> > > +1
> >> > >
> >> > > Follow me on   @BigData73
> >> > >
> >> > > -----Original Message-----
> >> > > From: Gunther Hagleitner [mailto:ghagleit...@hortonworks.com]
> >> > > Sent: Tuesday, October 07, 2014 7:27 PM
> >> > > To: dev@hive.apache.org
> >> > > Subject: Re: [VOTE] officially stop supporting hadoop 0.20.x in hive
> >> > 0.14 ?
> >> > >
> >> > > +1
> >> > >
> >> > > On Tue, Oct 7, 2014 at 4:20 PM, Lefty Leverenz <
> >> leftylever...@gmail.com>
> >> > > wrote:
> >> > >
> >> > >> <soapbox> Only if the Requirements
> >> > >> <
> >> > >>
> >> https://cwiki.apache.org/confluence/display/Hive/GettingStarted#Gettin
> >> > >> gStarted-Requirements
> >> > >> >
> >> > >> section of Getting Started gets updated (HIVE-7444
> >> > >> <https://issues.apache.org/jira/browse/HIVE-7444>). </soapbox>
> >> > >>
> >> > >> -- Lefty
> >> > >>
> >> > >> On Tue, Oct 7, 2014 at 7:18 PM, Sergey Shelukhin
> >> > >> <ser...@hortonworks.com>
> >> > >> wrote:
> >> > >>
> >> > >> > +1
> >> > >> >
> >> > >> > On Tue, Oct 7, 2014 at 4:15 PM, Prasanth Jayachandran <
> >> > >> > pjayachand...@hortonworks.com> wrote:
> >> > >> >
> >> > >> > > +1
> >> > >> > >
> >> > >> > > Thanks
> >> > >> > > Prasanth Jayachandran
> >> > >> > >
> >> > >> > > On Oct 7, 2014, at 4:13 PM, Eugene Koifman
> >> > >> > > <ekoif...@hortonworks.com>
> >> > >> > > wrote:
> >> > >> > >
> >> > >> > > > +1
> >> > >> > > >
> >> > >> > > > On Tue, Oct 7, 2014 at 4:10 PM, Vaibhav Gumashta <
> >> > >> > > vgumas...@hortonworks.com>
> >> > >> > > > wrote:
> >> > >> > > >
> >> > >> > > >> +1.
> >> > >> > > >>
> >> > >> > > >> Thanks,
> >> > >> > > >> --Vaibhav
> >> > >> > > >>
> >> > >> > > >> On Tue, Oct 7, 2014 at 3:53 PM, Thejas Nair
> >> > >> > > >> <the...@hortonworks.com
> >> > >> >
> >> > >> > > >> wrote:
> >> > >> > > >>
> >> > >> > > >>> I think it is time to revisit the support for hive support
> for
> >> > >> hadoop
> >> > >> > > >>> 0.20. Trying to maintain support for it puts additional
> burden
> >> > >> > > >>> on
> >> > >> > hive
> >> > >> > > >>> contributors.
> >> > >> > > >>>
> >> > >> > > >>> The last hadoop 0.20.x version was released on Feb 2010.
> >> > >> > > >>> Hadoop 1.0 was released in Dec 2011.
> >> > >> > > >>> I believe most users have moved on to hadoop 2.x or at
> least
> >> > >> > > >>> hadoop 1.x . The users if any that are still on hadoop 0.20
> >> > >> > > >>> probably don't tend to upgrade their hive versions as well.
> >> > >> > > >>>
> >> > >> > > >>> With the move to maven for builds in hive 0.13, we don't
> have
> >> > >> > > >>> the ability to compile against hadoop 0.20. (Nobody has
> >> > >> > > >>> complains about that AFAIK). I am not sure if hive 0.13
> works
> >> > >> > > >>> well against hadoop 0.20, as it is not clear if that
> >> > >> > > >>> combination is in use. Also, most commercial vendors seem
> to
> >> > >> > > >>> be focussing on testing it against
> >> > >> hadoop
> >> > >> > > >>> 2.x.
> >> > >> > > >>>
> >> > >> > > >>> I think it is time to do away with this added burden of
> >> > >> > > >>> attempting
> >> > >> to
> >> > >> > > >>> support hadoop 0.20.x versions.
> >> > >> > > >>>
> >> > >> > > >>> Here is my +1 for officially stopping support for hadoop
> >> > >> > > >>> 0.20.x in
> >> > >> > hive
> >> > >> > > >>> 0.14 .
> >> > >> > > >>>
> >> > >> > > >>> Thanks,
> >> > >> > > >>> Thejas
> >> > >> > > >>>
> >> > >> > > >>> --
> >> > >> > > >>> 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.
> >> > >> > > >>>
> >> > >> > > >>
> >> > >> > > >> --
> >> > >> > > >> 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.
> >> > >> > > >>
> >> > >> > > >
> >> > >> > > >
> >> > >> > > >
> >> > >> > > > --
> >> > >> > > >
> >> > >> > > > Thanks,
> >> > >> > > > Eugene
> >> > >> > > >
> >> > >> > > > --
> >> > >> > > > 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.
> >> > >> > >
> >> > >> > >
> >> > >> > > --
> >> > >> > > 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.
> >> > >> > >
> >> > >> >
> >> > >> > --
> >> > >> > 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.
> >> > >> >
> >> > >>
> >> > >
> >> > > --
> >> > > 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.
> >> >
> >> > --
> >> > 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.
> >> >
> >>
>
> --
> 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