Note that upgrading the minimum required version to JDK8 also gives Hive
the option of using more recent versions of several libraries including
hikaricp (as default connection pool option) [1] and jetty [2]

[1] https://issues.apache.org/jira/browse/HIVE-13931
[2] https://issues.apache.org/jira/browse/HIVE-16049


On Tue, Feb 28, 2017 at 7:45 AM, Sergio Pena <sergio.p...@cloudera.com>
wrote:

> Thanks Alan for the proposal. JDK8 seems to have very useful API. It should
> be good to start using it.
>
> +1.
>
> On Tue, Feb 28, 2017 at 12:55 AM, Rajat Khandelwal <
> rajat.khandel...@inmobi.com> wrote:
>
> > +1
> >
> > On Tue, Feb 28, 2017 at 10:37 AM, Prasanth Jayachandran <
> > pjayachand...@hortonworks.com> wrote:
> >
> > > +1
> > >
> > > Thanks
> > > Prasanth
> > >
> > >
> > >
> > >
> > > On Mon, Feb 27, 2017 at 8:55 PM -0800, "Thejas Nair" <
> > > thejas.n...@gmail.com<mailto:thejas.n...@gmail.com>> wrote:
> > >
> > >
> > > There was a [DISCUSS] thread on the topic of moving to jdk8 for unit
> > tests
> > > [1], and many people also expressed the opinion that we should drop
> JDK 7
> > > support in Hive. Public updates by Oracle was stopped on Apr 2015 [2].
> > >
> > > This vote thread proposes to dropping JDK 7 support in the next Apache
> > Hive
> > > 2.x release (ie master branch), so that we can start leveraging new
> > > features in Java 8 and also libraries that require java8.
> > >
> > > [1] https://s.apache.org/hive-jdk8-test
> > > [2] http://www.oracle.com/technetwork/java/eol-135779.html
> > >
> > > Here is my +1.
> > >
> > > Vote ends in 72 hours.
> > > Thanks,
> > > Thejas
> > >
> > > PS: I think this would fall under "Code change" under Hive-bylaws, so
> it
> > > doesn't seem to really require a formal vote thread. But I think this
> > does
> > > merit wider attention than a jira ticket.
> > >
> > >
> >
> >
> > --
> > Rajat Khandelwal
> > Tech Lead
> >
> > --
> > _____________________________________________________________
> > The information contained in this communication is intended solely for
> the
> > use of the individual or entity to whom it is addressed and others
> > authorized to receive it. It may contain confidential or legally
> privileged
> > information. If you are not the intended recipient you are hereby
> notified
> > that any disclosure, copying, distribution or taking any action in
> reliance
> > on the contents of this information is strictly prohibited and may be
> > unlawful. If you have received this communication in error, please notify
> > us immediately by responding to this email and then delete it from your
> > system. The firm is neither liable for the proper and complete
> transmission
> > of the information contained in this communication nor for any delay in
> its
> > receipt.
> >
>

Reply via email to