You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@drill.apache.org by andrew <an...@primer.org> on 2015/07/09 03:41:49 UTC
Allow Java 1.8
Hi,
Is there a reason we have an enforcement on Java versions as defined in the top-level pom.xml: [1.7, 1.8)? The code compiles for me just fine w/1.8. Is this merely
historical residue that can be relaxed or is there some deeper reason why Drill won’t/can’t work with 1.8?
Thanks,
Andrew
Re: Allow Java 1.8
Posted by Aditya <ad...@gmail.com>.
Most of the actual tasks to support JDK 8 were completed as sub-tasks of
DRILL-1491[1]
The only pending issue were few unit test failures DRILL-1489[2], which I
have not been able to reproduce till date, either on Windows or Linux.
If couple of other folks could take a stab and confirm either way, we could
start supporting JDK-8 from 1.2 release.
[1] https://issues.apache.org/jira/browse/DRILL-1491
[2] https://issues.apache.org/jira/browse/DRILL-1489
On Thu, Jul 9, 2015 at 12:44 AM, <mi...@nomura.com> wrote:
> I agree this would be very useful. Currently our Hadoop cluster and Spark
> are running on Java 1.8 and Drill is the only component left on 1.7, so
> ideally we could remove the reliance the older version of Java.
>
> Previously I have done some testing on Drill 1.0 on Java 1.8 and didn't
> hit any issues myself.
>
>
> -----Original Message-----
> From: Jacques Nadeau [mailto:jacques@apache.org]
> Sent: 09 July 2015 03:36
> To: dev@drill.apache.org
> Subject: Re: Allow Java 1.8
>
> Agreed. 7 and 8.
>
> On Wed, Jul 8, 2015 at 7:35 PM, David Tucker <dt...@maprtech.com> wrote:
>
> > I assume that “move to Java 1.8” implies “support Java 1.8 as well as
> > Java 1.7”, not “support Java 1.8 and exclude Java 1.7”.
> >
> > Regards,
> > David
> >
> > > On Jul 8, 2015, at 7:17 PM, Jacques Nadeau <ja...@apache.org> wrote:
> > >
> > > I don't think there is a good reason. I think the main issue was
> > > (at
> > some
> > > point) the tests weren't working with Java 8. Do you want to try to
> > > run the complete test suite and see if we have outstanding issues to
> > > move to Java 8?
> > >
> > > Aditya might remember more...
> > >
> > > On Wed, Jul 8, 2015 at 6:41 PM, andrew <an...@primer.org> wrote:
> > >
> > >> Hi,
> > >>
> > >> Is there a reason we have an enforcement on Java versions as
> > >> defined in the top-level pom.xml: [1.7, 1.8)? The code compiles for
> > >> me just fine w/1.8. Is this merely historical residue that can be
> > >> relaxed or is there some deeper reason
> > why
> > >> Drill won’t/can’t work with 1.8?
> > >>
> > >> Thanks,
> > >> Andrew
> >
> >
>
>
> This e-mail (including any attachments) is private and confidential, may
> contain proprietary or privileged information and is intended for the named
> recipient(s) only. Unintended recipients are strictly prohibited from
> taking action on the basis of information in this e-mail and must contact
> the sender immediately, delete this e-mail (and all attachments) and
> destroy any hard copies. Nomura will not accept responsibility or liability
> for the accuracy or completeness of, or the presence of any virus or
> disabling code in, this e-mail. If verification is sought please request a
> hard copy. Any reference to the terms of executed transactions should be
> treated as preliminary only and subject to formal written confirmation by
> Nomura. Nomura reserves the right to retain, monitor and intercept e-mail
> communications through its networks (subject to and in accordance with
> applicable laws). No confidentiality or privilege is waived or lost by
> Nomura by any mistransmission of this e-mail. Any reference to "Nomura" is
> a reference to any entity in the Nomura Holdings, Inc. group. Please read
> our Electronic Communications Legal Notice which forms part of this e-mail:
> http://www.Nomura.com/email_disclaimer.htm
>
>
RE: Allow Java 1.8
Posted by mi...@nomura.com.
I agree this would be very useful. Currently our Hadoop cluster and Spark are running on Java 1.8 and Drill is the only component left on 1.7, so ideally we could remove the reliance the older version of Java.
Previously I have done some testing on Drill 1.0 on Java 1.8 and didn't hit any issues myself.
-----Original Message-----
From: Jacques Nadeau [mailto:jacques@apache.org]
Sent: 09 July 2015 03:36
To: dev@drill.apache.org
Subject: Re: Allow Java 1.8
Agreed. 7 and 8.
On Wed, Jul 8, 2015 at 7:35 PM, David Tucker <dt...@maprtech.com> wrote:
> I assume that “move to Java 1.8” implies “support Java 1.8 as well as
> Java 1.7”, not “support Java 1.8 and exclude Java 1.7”.
>
> Regards,
> David
>
> > On Jul 8, 2015, at 7:17 PM, Jacques Nadeau <ja...@apache.org> wrote:
> >
> > I don't think there is a good reason. I think the main issue was
> > (at
> some
> > point) the tests weren't working with Java 8. Do you want to try to
> > run the complete test suite and see if we have outstanding issues to
> > move to Java 8?
> >
> > Aditya might remember more...
> >
> > On Wed, Jul 8, 2015 at 6:41 PM, andrew <an...@primer.org> wrote:
> >
> >> Hi,
> >>
> >> Is there a reason we have an enforcement on Java versions as
> >> defined in the top-level pom.xml: [1.7, 1.8)? The code compiles for
> >> me just fine w/1.8. Is this merely historical residue that can be
> >> relaxed or is there some deeper reason
> why
> >> Drill won’t/can’t work with 1.8?
> >>
> >> Thanks,
> >> Andrew
>
>
This e-mail (including any attachments) is private and confidential, may contain proprietary or privileged information and is intended for the named recipient(s) only. Unintended recipients are strictly prohibited from taking action on the basis of information in this e-mail and must contact the sender immediately, delete this e-mail (and all attachments) and destroy any hard copies. Nomura will not accept responsibility or liability for the accuracy or completeness of, or the presence of any virus or disabling code in, this e-mail. If verification is sought please request a hard copy. Any reference to the terms of executed transactions should be treated as preliminary only and subject to formal written confirmation by Nomura. Nomura reserves the right to retain, monitor and intercept e-mail communications through its networks (subject to and in accordance with applicable laws). No confidentiality or privilege is waived or lost by Nomura by any mistransmission of this e-mail. Any reference to "Nomura" is a reference to any entity in the Nomura Holdings, Inc. group. Please read our Electronic Communications Legal Notice which forms part of this e-mail: http://www.Nomura.com/email_disclaimer.htm
Re: Allow Java 1.8
Posted by Jacques Nadeau <ja...@apache.org>.
Agreed. 7 and 8.
On Wed, Jul 8, 2015 at 7:35 PM, David Tucker <dt...@maprtech.com> wrote:
> I assume that “move to Java 1.8” implies “support Java 1.8 as well as Java
> 1.7”, not “support Java 1.8 and exclude Java 1.7”.
>
> Regards,
> David
>
> > On Jul 8, 2015, at 7:17 PM, Jacques Nadeau <ja...@apache.org> wrote:
> >
> > I don't think there is a good reason. I think the main issue was (at
> some
> > point) the tests weren't working with Java 8. Do you want to try to run
> > the complete test suite and see if we have outstanding issues to move to
> > Java 8?
> >
> > Aditya might remember more...
> >
> > On Wed, Jul 8, 2015 at 6:41 PM, andrew <an...@primer.org> wrote:
> >
> >> Hi,
> >>
> >> Is there a reason we have an enforcement on Java versions as defined in
> >> the top-level pom.xml: [1.7, 1.8)? The code compiles for me just fine
> >> w/1.8. Is this merely
> >> historical residue that can be relaxed or is there some deeper reason
> why
> >> Drill won’t/can’t work with 1.8?
> >>
> >> Thanks,
> >> Andrew
>
>
Re: Allow Java 1.8
Posted by David Tucker <dt...@maprtech.com>.
I assume that “move to Java 1.8” implies “support Java 1.8 as well as Java 1.7”, not “support Java 1.8 and exclude Java 1.7”.
Regards,
David
> On Jul 8, 2015, at 7:17 PM, Jacques Nadeau <ja...@apache.org> wrote:
>
> I don't think there is a good reason. I think the main issue was (at some
> point) the tests weren't working with Java 8. Do you want to try to run
> the complete test suite and see if we have outstanding issues to move to
> Java 8?
>
> Aditya might remember more...
>
> On Wed, Jul 8, 2015 at 6:41 PM, andrew <an...@primer.org> wrote:
>
>> Hi,
>>
>> Is there a reason we have an enforcement on Java versions as defined in
>> the top-level pom.xml: [1.7, 1.8)? The code compiles for me just fine
>> w/1.8. Is this merely
>> historical residue that can be relaxed or is there some deeper reason why
>> Drill won’t/can’t work with 1.8?
>>
>> Thanks,
>> Andrew
Re: Allow Java 1.8
Posted by Jacques Nadeau <ja...@apache.org>.
I don't think there is a good reason. I think the main issue was (at some
point) the tests weren't working with Java 8. Do you want to try to run
the complete test suite and see if we have outstanding issues to move to
Java 8?
Aditya might remember more...
On Wed, Jul 8, 2015 at 6:41 PM, andrew <an...@primer.org> wrote:
> Hi,
>
> Is there a reason we have an enforcement on Java versions as defined in
> the top-level pom.xml: [1.7, 1.8)? The code compiles for me just fine
> w/1.8. Is this merely
> historical residue that can be relaxed or is there some deeper reason why
> Drill won’t/can’t work with 1.8?
>
> Thanks,
> Andrew