Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 31CEC200CC4 for ; Thu, 13 Jul 2017 11:25:55 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 3024016BBF7; Thu, 13 Jul 2017 09:25:55 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 7FA4716BBF5 for ; Thu, 13 Jul 2017 11:25:53 +0200 (CEST) Received: (qmail 56833 invoked by uid 500); 13 Jul 2017 09:25:52 -0000 Mailing-List: contact user-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list user@flink.apache.org Received: (qmail 56813 invoked by uid 99); 13 Jul 2017 09:25:52 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Jul 2017 09:25:52 +0000 Received: from mail-pg0-f48.google.com (mail-pg0-f48.google.com [74.125.83.48]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id C4F2B1A05A0; Thu, 13 Jul 2017 09:25:51 +0000 (UTC) Received: by mail-pg0-f48.google.com with SMTP id j186so26774008pge.2; Thu, 13 Jul 2017 02:25:51 -0700 (PDT) X-Gm-Message-State: AIVw110AzSfJaMLa2l/xyrTLEbL+Uy/ppmqlBvf+VgkNdCNm3T9+Mutx ctQfyovDJK1gvtAU+KIqG9AgVPr9sg== X-Received: by 10.98.160.133 with SMTP id p5mr59428827pfl.226.1499937951322; Thu, 13 Jul 2017 02:25:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.163.102 with HTTP; Thu, 13 Jul 2017 02:25:35 -0700 (PDT) In-Reply-To: <1844e107-04f1-3210-db44-637fa3571aaf@tngtech.com> References: <596643fe.4692370a.18459.b950@mx.google.com> <1844e107-04f1-3210-db44-637fa3571aaf@tngtech.com> From: Stephan Ewen Date: Thu, 13 Jul 2017 11:25:35 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [POLL] Who still uses Java 7 with Flink ? To: "dev@flink.apache.org" , user Content-Type: multipart/alternative; boundary="001a11417a1ec6178e05542f840d" archived-at: Thu, 13 Jul 2017 09:25:55 -0000 --001a11417a1ec6178e05542f840d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks a lot for the feedback. Let's keep this thread open for feedback till end of the week. If it stays like it is (all or a vast majority in favor of dropping Java 7 support), we should start dropping Java 7 from next week on. On Thu, Jul 13, 2017 at 10:59 AM, Konstantin Knauf < konstantin.knauf@tngtech.com> wrote: > +1 for dropping Java 7 > > On 13.07.2017 10:11, Niels Basjes wrote: > > +1 For dropping java 1.7 > > > > On 13 Jul 2017 04:11, "Jark Wu" wrote: > > > >> +1 for dropping Java 7 > >> > >> 2017-07-13 9:34 GMT+08:00 =E2=98=BC R Nair (=E0=A4=B0=E0=A4=B5=E0=A4= =BF=E0=A4=B6=E0=A4=82=E0=A4=95=E0=A4=B0 =E0=A4=A8=E0=A4=BE=E0=A4=AF=E0=A4= =B0) < > >> ravishankar.nair@gmail.com>: > >> > >>> +1 for dropping Java 1.7. > >>> > >>> On Wed, Jul 12, 2017 at 9:10 PM, Kurt Young wrote: > >>> > >>>> +1 for droppint Java 7, we have been using Java 8 for more than one > year > >>>> in Alibaba and everything work fine. > >>>> > >>>> Best, > >>>> Kurt > >>>> > >>>> On Thu, Jul 13, 2017 at 2:53 AM, Bowen Li > >>>> wrote: > >>>> > >>>>> +1 for dropping Java 7 > >>>>> > >>>>> On Wed, Jul 12, 2017 at 9:04 AM, Gyula F=C3=B3ra > >>>>> wrote: > >>>>> > >>>>>> +1 for dropping 1.7 from me as well. > >>>>>> > >>>>>> Gyula > >>>>>> > >>>>>> On Wed, Jul 12, 2017, 17:53 Ted Yu wrote: > >>>>>> > >>>>>>> +1 on dropping support for Java 1.7 > >>>>>>> > >>>>>>> -------- Original message -------- > >>>>>>> From: Robert Metzger > >>>>>>> Date: 7/12/17 8:36 AM (GMT-08:00) > >>>>>>> To: dev@flink.apache.org > >>>>>>> Cc: user > >>>>>>> Subject: Re: [POLL] Who still uses Java 7 with Flink ? > >>>>>>> > >>>>>>> +1 to drop Java 7 support > >>>>>>> > >>>>>>> I believe that we can move to Java 8 for the argument you've > stated. > >>>>>>> ElasticSearch 5, Spark 2.2 require Java 8 already, Hadoop 3.0.0 > >>>>> will > >>>>>>> require it as well. > >>>>>>> > >>>>>>> On Wed, Jul 12, 2017 at 4:02 PM, Driesprong, Fokko > >>>>> >>>>>>> > >>>>>>> wrote: > >>>>>>> > >>>>>>>> Hi, > >>>>>>>> > >>>>>>>> I would be in favor of dropping Java 7 as we don't use it in our > >>>>> hadoop > >>>>>>>> infra (and we are a bank). Also, Spark 2.2 has been released > today, > >>>>>>>> which doesn't > >>>>>>>> support Java 7 >>>>> ses/spark-release-2-2-0. > >>>>>> html > >>>>>>>>> > >>>>>>>> anymore, and Flink should not lack behind :-) > >>>>>>>> > >>>>>>>> Cheers, Fokko > >>>>>>>> > >>>>>>>> 2017-07-12 15:56 GMT+02:00 Stephan Ewen : > >>>>>>>> > >>>>>>>>> Bumping this thread again. > >>>>>>>>> > >>>>>>>>> There are several strong points for dropping Java 7 support, > >>>>> apart > >>>>>> from > >>>>>>>> the > >>>>>>>>> fact that it is not maintained > >>>>>>>>> > >>>>>>>>> - We could really use the Java 8 default methods feature in > >>>>>>>> interfaces to > >>>>>>>>> evolve the API without breaking backwards compatibility > >>>>>>>>> > >>>>>>>>> - Easier build setup for Scala 2.12 (which requires Java 8), > >>>>> no need > >>>>>>>> to > >>>>>>>>> manage the tricky combinations of Java / Scala versions > >>>>>>>>> > >>>>>>>>> - Ability to use vanilla Akka (rather than Flakka) which > >>>>> requires > >>>>>>>> Java 8. > >>>>>>>>> - Fewer problems for users that use Akka in the Flink > >>>>> applications > >>>>>>>>> - Flakka currently does not support Scala 2.12 > >>>>>>>>> - Newer Akka versions shade protobuf, which is important > >>>>>>>>> > >>>>>>>>> I think these together make a pretty good case for bumping the > >>>>>> required > >>>>>>>>> Java version to Java 8. > >>>>>>>>> > >>>>>>>>> It would just help both Flink users (dependency management, Sca= la > >>>>>>>> versions) > >>>>>>>>> and developers (build simplification) a lot. > >>>>>>>>> Unless we see users stepping forward and making a case that it > >>>>> will be > >>>>>>>>> impossible for them to upgrade to Java 8, I suggest to go > >>>>> forward with > >>>>>>>>> this. > >>>>>>>>> > >>>>>>>>> Best, > >>>>>>>>> Stephan > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> On Thu, Jun 8, 2017 at 9:36 PM, Haohui Mai > >>>>>> wrote: > >>>>>>>>> > >>>>>>>>>> +1 > >>>>>>>>>> > >>>>>>>>>> There are several high impacts security vulnerabilities in JDK > >>>>> 7 and > >>>>>>>> will > >>>>>>>>>> not be addressed. > >>>>>>>>>> > >>>>>>>>>> As a result we completely moved away from JDK 7. > >>>>>>>>>> > >>>>>>>>>> +1 on separating the tasks of supporting Scala 2.12 and JDK 8 > >>>>> in two > >>>>>>>>> steps. > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> On Thu, Jun 8, 2017 at 9:53 AM Greg Hogan > >>>>>> wrote: > >>>>>>>>>> > >>>>>>>>>>> Is this not two different issues? > >>>>>>>>>>> - adding builds for Scala 2.12 > >>>>>>>>>>> - upgrading to Java version 1.8 > >>>>>>>>>>> > >>>>>>>>>>> It may be time to switch, but I haven=E2=80=99t seen anything= in > >>>>>> FLINK-5005 > >>>>>>>>> which > >>>>>>>>>>> prevents simply adding Scala 2.12 to our supported build > >>>>> matrix > >>>>>> and > >>>>>>>>>>> continuing to build 2.10 / 2.11 against Java 1.7. > >>>>>>>>>>> > >>>>>>>>>>> Greg > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>>> On Jun 8, 2017, at 11:39 AM, Robert Metzger < > >>>>>> rmetzger@apache.org> > >>>>>>>>>> wrote: > >>>>>>>>>>>> > >>>>>>>>>>>> Hi all, > >>>>>>>>>>>> > >>>>>>>>>>>> as promised in March, I want to revive this discussion! > >>>>>>>>>>>> > >>>>>>>>>>>> Our users are begging for Scala 2.12 support [1], > >>>>> migration to > >>>>>>>> Akka > >>>>>>>>> 2.4 > >>>>>>>>>>> would solve a bunch of shading / dependency issues (Akka 2.4 > >>>>> will > >>>>>>>>> remove > >>>>>>>>>>> Akka's protobuf dependency [2][3]) and generally Java 8's new > >>>>>>>> language > >>>>>>>>>>> features all speak for dropping Java 7. > >>>>>>>>>>>> > >>>>>>>>>>>> Java 8 has been released in March, 2014. Java 7 is > >>>>> unsupported > >>>>>>>> since > >>>>>>>>>>> June 2016. > >>>>>>>>>>>> > >>>>>>>>>>>> So what's the feeling in the community regarding the step? > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> [1] https://issues.apache.org/jira/browse/FLINK-5005# < > >>>>>>>>>>> https://issues.apache.org/jira/browse/FLINK-5005#> > >>>>>>>>>>>> [2] https://issues.apache.org/jira/browse/FLINK-5989 < > >>>>>>>>>>> https://issues.apache.org/jira/browse/FLINK-5989> > >>>>>>>>>>>> [3] > >>>>>>>>>>> https://issues.apache.org/jira/browse/FLINK-3211? > >>>>>>>>>> focusedCommentId=3D15274018&page=3Dcom.atlassian.jira. > >>>>>>>>>> plugin.system.issuetabpanels:comment-tabpanel#comment-15274018 > >>>>>>>>>>> < > >>>>>>>>>>> https://issues.apache.org/jira/browse/FLINK-3211? > >>>>>>>>>> focusedCommentId=3D15274018&page=3Dcom.atlassian.jira. > >>>>>>>>>> plugin.system.issuetabpanels:comment-tabpanel#comment-15274018 > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> On Thu, Mar 23, 2017 at 2:42 PM, Theodore Vasiloudis < > >>>>>>>>>>> theodoros.vasiloudis@gmail.com >>>>>>>> theodoros.vasiloudis@gmail.com > >>>>>>>>>>> > >>>>>>>>>>> wrote: > >>>>>>>>>>>> Hello all, > >>>>>>>>>>>> > >>>>>>>>>>>> I'm sure you've considered this already, but what this > >>>>> data does > >>>>>>>> not > >>>>>>>>>>> include is all the potential future users, > >>>>>>>>>>>> i.e. slower moving organizations (banks etc.) which could > >>>>> be on > >>>>>>>> Java > >>>>>>>>> 7 > >>>>>>>>>>> still. > >>>>>>>>>>>> > >>>>>>>>>>>> Whether those are relevant is up for debate. > >>>>>>>>>>>> > >>>>>>>>>>>> Cheers, > >>>>>>>>>>>> Theo > >>>>>>>>>>>> > >>>>>>>>>>>> On Thu, Mar 23, 2017 at 12:14 PM, Robert Metzger < > >>>>>>>>> rmetzger@apache.org > >>>>>>>>>>> > wrote: > >>>>>>>>>>>> Yeah, you are right :) > >>>>>>>>>>>> I'll put something in my calendar for end of May. > >>>>>>>>>>>> > >>>>>>>>>>>> On Thu, Mar 23, 2017 at 12:12 PM, Greg Hogan < > >>>>>> code@greghogan.com > >>>>>>>>>>> > wrote: > >>>>>>>>>>>> Robert, > >>>>>>>>>>>> > >>>>>>>>>>>> Thanks for the report. Shouldn=E2=80=99t we be revisiting th= is > >>>>> decision > >>>>>> at > >>>>>>>>> the > >>>>>>>>>>> beginning of the new release cycle rather than near the end? > >>>>> There > >>>>>>>> is > >>>>>>>>>>> currently little cost to staying with Java 7 since no Flink > >>>>> code > >>>>>> or > >>>>>>>>> pull > >>>>>>>>>>> requests have been written for Java 8. > >>>>>>>>>>>> > >>>>>>>>>>>> Greg > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>>> On Mar 23, 2017, at 6:37 AM, Robert Metzger < > >>>>>> rmetzger@apache.org > >>>>>>>>>>> > wrote: > >>>>>>>>>>>>> > >>>>>>>>>>>>> Looks like 9% on twitter and 24% on the mailing list are > >>>>> still > >>>>>>>> using > >>>>>>>>>>> Java 7. > >>>>>>>>>>>>> > >>>>>>>>>>>>> I would vote to keep supporting Java 7 for Flink 1.3 and > >>>>> then > >>>>>>>>> revisit > >>>>>>>>>>> once we are approaching 1.4 in September. > >>>>>>>>>>>>> > >>>>>>>>>>>>> On Thu, Mar 16, 2017 at 8:00 AM, Bowen Li < > >>>>>>>> bowen.li@offerupnow.com > >>>>>>>>>>> > wrote: > >>>>>>>>>>>>> There's always a tradeoff we need to make. I'm in favor of > >>>>>>>> upgrading > >>>>>>>>>> to > >>>>>>>>>>> Java 8 to bring in all new Java features. > >>>>>>>>>>>>> > >>>>>>>>>>>>> The common way I've seen (and I agree) other software > >>>>> upgrading > >>>>>>>>> major > >>>>>>>>>>> things like this is 1) upgrade for next big release without > >>>>>> backward > >>>>>>>>>>> compatibility and notify everyone 2) maintain and patch > >>>>> current, > >>>>>>>>> old-tech > >>>>>>>>>>> compatible version at a reasonably limited scope. Building > >>>>>> backward > >>>>>>>>>>> compatibility is too much for an open sourced project > >>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>> On Wed, Mar 15, 2017 at 7:10 AM, Robert Metzger < > >>>>>>>>> rmetzger@apache.org > >>>>>>>>>>> > wrote: > >>>>>>>>>>>>> I've put it also on our Twitter account: > >>>>>>>>>>>>> https://twitter.com/ApacheFlink/status/842015062667755521 > >>>>> < > >>>>>>>>>>> https://twitter.com/ApacheFlink/status/842015062667755521> > >>>>>>>>>>>>> > >>>>>>>>>>>>> On Wed, Mar 15, 2017 at 2:19 PM, Martin Neumann < > >>>>>>>>> martin.neumann@ri.se > >>>>>>>>>>> > > >>>>>>>>>>>>> wrote: > >>>>>>>>>>>>> > >>>>>>>>>>>>>> I think this easier done in a straw poll than in an > >>>>> email > >>>>>>>>>>> conversation. > >>>>>>>>>>>>>> I created one at: http://www.strawpoll.me/12535073 < > >>>>>>>>>>> http://www.strawpoll.me/12535073> > >>>>>>>>>>>>>> (Note that you have multiple choices.) > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> Though I prefer Java 8 most of the time I have to work > >>>>> on > >>>>>> Java > >>>>>>>> 7. > >>>>>>>>> A > >>>>>>>>>>> lot of > >>>>>>>>>>>>>> the infrastructure I work on still runs Java 7, one of > >>>>> the > >>>>>>>>>> companies I > >>>>>>>>>>>>>> build a prototype for a while back just updated to Java > >>>>> 7 2 > >>>>>>>> years > >>>>>>>>>>> ago. I > >>>>>>>>>>>>>> doubt we can ditch Java 7 support any time soon if we > >>>>> want to > >>>>>>>> make > >>>>>>>>>> it > >>>>>>>>>>> easy > >>>>>>>>>>>>>> for companies to use Flink. > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> cheers Martin > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> //PS sorry if this gets sent twice, we just migrated to > >>>>> a new > >>>>>>>> mail > >>>>>>>>>>> system > >>>>>>>>>>>>>> and a lot of things are broken > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> ________________________________ > >>>>>>>>>>>>>> From: Stephan Ewen >>>>>> sewen@apache.org > >>>>>>>>>> > >>>>>>>>>>>>>> Sent: Wednesday, March 15, 2017 12:30:24 PM > >>>>>>>>>>>>>> To: user@flink.apache.org >>>>>> ; > >>>>>>>>>>> dev@flink.apache.org > >>>>>>>>>>>>>> Subject: [POLL] Who still uses Java 7 with Flink ? > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> Hi all! > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> I would like to get a feeling how much Java 7 is still > >>>>> being > >>>>>>>> used > >>>>>>>>>>> among > >>>>>>>>>>>>>> Flink users. > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> At some point, it would be great to drop Java 7 support > >>>>> and > >>>>>>>> make > >>>>>>>>> use > >>>>>>>>>>> of > >>>>>>>>>>>>>> Java 8's new features, but first we would need to get a > >>>>>> feeling > >>>>>>>>> how > >>>>>>>>>>> much > >>>>>>>>>>>>>> Java 7 is still used. > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> Would be happy if users on Java 7 respond here, or even > >>>>> users > >>>>>>>> that > >>>>>>>>>>> have > >>>>>>>>>>>>>> some insights into how widespread they think Java 7 > >>>>> still is. > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> Thanks, > >>>>>>>>>>>>>> Stephan > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>> > >>>>>>>>> > >>>>>>>> > >>>>>>> > >>>>>>> > >>>>>> > >>>>> > >>>> > >>>> > >>> > >>> > >>> -- > >>> > >>> > >> > > > > -- > Konstantin Knauf * konstantin.knauf@tngtech.com * +49-174-3413182 > TNG Technology Consulting GmbH, Betastr. 13a, 85774 Unterf=C3=B6hring > Gesch=C3=A4ftsf=C3=BChrer: Henrik Klagges, Christoph Stock, Dr. Robert Da= hlke > Sitz: Unterf=C3=B6hring * Amtsgericht M=C3=BCnchen * HRB 135082 > --001a11417a1ec6178e05542f840d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks a lot for the feedback. Let's keep this thread = open for feedback till end of the week.

If it stays like= it is (all or a vast majority in favor of dropping Java 7 support), we sho= uld start dropping Java 7 from next week on.


On Th= u, Jul 13, 2017 at 10:59 AM, Konstantin Knauf <konstantin.knauf= @tngtech.com> wrote:
+1 for dropping Java 7

On 13.07.2017 10:11, Niels B= asjes wrote:
> +1 For dropping java 1.7
>
> On 13 Jul 2017 04:11, "Jark Wu" <jark@apache.org> wrote:
>
>> +1 for dropping Java 7
>>
>> 2017-07-13 9:34 GMT+08:00 =E2=98=BC R Nair (=E0=A4=B0=E0=A4=B5=E0= =A4=BF=E0=A4=B6=E0=A4=82=E0=A4=95=E0=A4=B0 =E0=A4=A8=E0=A4=BE=E0=A4=AF=E0= =A4=B0) <
>> ravishankar.nair@gma= il.com>:
>>
>>> +1 for dropping Java 1.7.
>>>
>>> On Wed, Jul 12, 2017 at 9:10 PM, Kurt Young <ykt836@gmail.com> wrote:
>>>
>>>> +1 for droppint Java 7, we have been using Java 8 for more= than one year
>>>> in Alibaba and everything work fine.
>>>>
>>>> Best,
>>>> Kurt
>>>>
>>>> On Thu, Jul 13, 2017 at 2:53 AM, Bowen Li <bowen.li@offerupnow.com>
>>>> wrote:
>>>>
>>>>> +1 for dropping Java 7
>>>>>
>>>>> On Wed, Jul 12, 2017 at 9:04 AM, Gyula F=C3=B3ra <<= a href=3D"mailto:gyula.fora@gmail.com">gyula.fora@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> +1 for dropping 1.7 from me as well.
>>>>>>
>>>>>> Gyula
>>>>>>
>>>>>> On Wed, Jul 12, 2017, 17:53 Ted Yu <yuzhihong@gmail.com> wrote:
>>>>>>
>>>>>>> +1 on dropping support for Java 1.7
>>>>>>>
>>>>>>> -------- Original message --------
>>>>>>> From: Robert Metzger <rmetzger@apache.org>
>>>>>>> Date: 7/12/17 8:36 AM (GMT-08:00)
>>>>>>> To: de= v@flink.apache.org
>>>>>>> Cc: user <user@flink.apache.org>
>>>>>>> Subject: Re: [POLL] Who still uses Java 7 with= Flink ?
>>>>>>>
>>>>>>> +1 to drop Java 7 support
>>>>>>>
>>>>>>> I believe that we can move to Java 8 for the a= rgument you've stated.
>>>>>>> ElasticSearch 5, Spark 2.2=C2=A0 require Java = 8 already, Hadoop 3.0.0
>>>>> will
>>>>>>> require it as well.
>>>>>>>
>>>>>>> On Wed, Jul 12, 2017 at 4:02 PM, Driesprong, F= okko
>>>>> <fokko@driesprong.frl
>>>>>>>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I would be in favor of dropping Java 7 as = we don't use it in our
>>>>> hadoop
>>>>>>>> infra (and we are a bank). Also, Spark 2.2= has been released today,
>>>>>>>> which doesn't
>>>>>>>> support Java 7 <http://spark.apache= .org/relea
>>>>> ses/spark-release-2-2-0.
>>>>>> html
>>>>>>>>>
>>>>>>>> anymore, and Flink should not lack behind = :-)
>>>>>>>>
>>>>>>>> Cheers, Fokko
>>>>>>>>
>>>>>>>> 2017-07-12 15:56 GMT+02:00 Stephan Ewen &l= t;sewen@apache.org>:
>>>>>>>>
>>>>>>>>> Bumping this thread again.
>>>>>>>>>
>>>>>>>>> There are several strong points for dr= opping Java 7 support,
>>>>> apart
>>>>>> from
>>>>>>>> the
>>>>>>>>> fact that it is not maintained
>>>>>>>>>
>>>>>>>>>=C2=A0 =C2=A0- We could really use the = Java 8 default methods feature in
>>>>>>>> interfaces to
>>>>>>>>> evolve the API without breaking backwa= rds compatibility
>>>>>>>>>
>>>>>>>>>=C2=A0 =C2=A0- Easier build setup for S= cala 2.12 (which requires Java 8),
>>>>> no need
>>>>>>>> to
>>>>>>>>> manage the tricky combinations of Java= / Scala versions
>>>>>>>>>
>>>>>>>>>=C2=A0 =C2=A0- Ability to use vanilla A= kka (rather than Flakka) which
>>>>> requires
>>>>>>>> Java 8.
>>>>>>>>>=C2=A0 =C2=A0 =C2=A0- Fewer problems fo= r users that use Akka in the Flink
>>>>> applications
>>>>>>>>>=C2=A0 =C2=A0 =C2=A0- Flakka currently = does not support Scala 2.12
>>>>>>>>>=C2=A0 =C2=A0 =C2=A0- Newer Akka versio= ns shade protobuf, which is important
>>>>>>>>>
>>>>>>>>> I think these together make a pretty g= ood case for bumping the
>>>>>> required
>>>>>>>>> Java version to Java 8.
>>>>>>>>>
>>>>>>>>> It would just help both Flink users (d= ependency management, Scala
>>>>>>>> versions)
>>>>>>>>> and developers (build simplification) = a lot.
>>>>>>>>> Unless we see users stepping forward a= nd making a case that it
>>>>> will be
>>>>>>>>> impossible for them to upgrade to Java= 8, I suggest to go
>>>>> forward with
>>>>>>>>> this.
>>>>>>>>>
>>>>>>>>> Best,
>>>>>>>>> Stephan
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Thu, Jun 8, 2017 at 9:36 PM, Haohui= Mai <ricetons@gmail.com> >>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> +1
>>>>>>>>>>
>>>>>>>>>> There are several high impacts sec= urity vulnerabilities in JDK
>>>>> 7 and
>>>>>>>> will
>>>>>>>>>> not be addressed.
>>>>>>>>>>
>>>>>>>>>> As a result we completely moved aw= ay from JDK 7.
>>>>>>>>>>
>>>>>>>>>> +1 on separating the tasks of supp= orting Scala 2.12 and JDK 8
>>>>> in two
>>>>>>>>> steps.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Thu, Jun 8, 2017 at 9:53 AM Gre= g Hogan <code@greghogan.com>= ;
>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Is this not two different issu= es?
>>>>>>>>>>> - adding builds for Scala 2.12=
>>>>>>>>>>> - upgrading to Java version 1.= 8
>>>>>>>>>>>
>>>>>>>>>>> It may be time to switch, but = I haven=E2=80=99t seen anything in
>>>>>> FLINK-5005
>>>>>>>>> which
>>>>>>>>>>> prevents simply adding Scala 2= .12 to our supported build
>>>>> matrix
>>>>>> and
>>>>>>>>>>> continuing to build 2.10 / 2.1= 1 against Java 1.7.
>>>>>>>>>>>
>>>>>>>>>>> Greg
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> On Jun 8, 2017, at 11:39 A= M, Robert Metzger <
>>>>>> rmetzger@ap= ache.org>
>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>
>>>>>>>>>>>> as promised in March, I wa= nt to revive this discussion!
>>>>>>>>>>>>
>>>>>>>>>>>> Our users are begging for = Scala 2.12 support [1],
>>>>> migration to
>>>>>>>> Akka
>>>>>>>>> 2.4
>>>>>>>>>>> would solve a bunch of shading= / dependency issues (Akka 2.4
>>>>> will
>>>>>>>>> remove
>>>>>>>>>>> Akka's protobuf dependency= [2][3]) and generally Java 8's new
>>>>>>>> language
>>>>>>>>>>> features all speak for droppin= g Java 7.
>>>>>>>>>>>>
>>>>>>>>>>>> Java 8 has been released i= n March, 2014. Java 7 is
>>>>> unsupported
>>>>>>>> since
>>>>>>>>>>> June 2016.
>>>>>>>>>>>>
>>>>>>>>>>>> So what's the feeling = in the community regarding the step?
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> [1] https://issues.apache.org/jira/browse/FLINK-5005# <
>>>>>>>>>>> https:= //issues.apache.org/jira/browse/FLINK-5005#>
>>>>>>>>>>>> [2] https://issues.apache.org/jira/browse/FLINK-5989 <
>>>>>>>>>>> https:/= /issues.apache.org/jira/browse/FLINK-5989>
>>>>>>>>>>>> [3]
>>>>>>>>>>> https:/= /issues.apache.org/jira/browse/FLINK-3211?
>>>>>>>>>> focusedCommentId=3D15274018&page=3Dcom.atlassian.jira.
>>>>>>>>>> plugin.system.issuetabpanels:= comment-tabpanel#comment-15274018
>>>>>>>>>>> <
>>>>>>>>>>> https:/= /issues.apache.org/jira/browse/FLINK-3211?
>>>>>>>>>> focusedCommentId=3D15274018&page=3Dcom.atlassian.jira.
>>>>>>>>>> plugin.system.issuetabpanels:= comment-tabpanel#comment-15274018
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Thu, Mar 23, 2017 at 2:= 42 PM, Theodore Vasiloudis <
>>>>>>>>>>> theodoros.vasiloudis@gmail.com <mailto:
>>>>>>>> theodoros.vasiloudis@gmail.com
>>>>>>>>>>>
>>>>>>>>>>> wrote:
>>>>>>>>>>>> Hello all,
>>>>>>>>>>>>
>>>>>>>>>>>> I'm sure you've co= nsidered this already, but what this
>>>>> data does
>>>>>>>> not
>>>>>>>>>>> include is all the potential f= uture users,
>>>>>>>>>>>> i.e. slower moving organiz= ations (banks etc.) which could
>>>>> be on
>>>>>>>> Java
>>>>>>>>> 7
>>>>>>>>>>> still.
>>>>>>>>>>>>
>>>>>>>>>>>> Whether those are relevant= is up for debate.
>>>>>>>>>>>>
>>>>>>>>>>>> Cheers,
>>>>>>>>>>>> Theo
>>>>>>>>>>>>
>>>>>>>>>>>> On Thu, Mar 23, 2017 at 12= :14 PM, Robert Metzger <
>>>>>>>>> rmetzger@apache.org
>>>>>>>>>>> <mailto:rmetzger@apache.org>> wrote:
>>>>>>>>>>>> Yeah, you are right :)
>>>>>>>>>>>> I'll put something in = my calendar for end of May.
>>>>>>>>>>>>
>>>>>>>>>>>> On Thu, Mar 23, 2017 at 12= :12 PM, Greg Hogan <
>>>>>> code@greghog= an.com
>>>>>>>>>>> <mailto:code@greghogan.com>> wrote:
>>>>>>>>>>>> Robert,
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks for the report. Sho= uldn=E2=80=99t we be revisiting this
>>>>> decision
>>>>>> at
>>>>>>>>> the
>>>>>>>>>>> beginning of the new release c= ycle rather than near the end?
>>>>> There
>>>>>>>> is
>>>>>>>>>>> currently little cost to stayi= ng with Java 7 since no Flink
>>>>> code
>>>>>> or
>>>>>>>>> pull
>>>>>>>>>>> requests have been written for= Java 8.
>>>>>>>>>>>>
>>>>>>>>>>>> Greg
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> On Mar 23, 2017, at 6:= 37 AM, Robert Metzger <
>>>>>> rmetzger@ap= ache.org
>>>>>>>>>>> <mailto:rmetzger@apache.org>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Looks like 9% on twitt= er and 24% on the mailing list are
>>>>> still
>>>>>>>> using
>>>>>>>>>>> Java 7.
>>>>>>>>>>>>>
>>>>>>>>>>>>> I would vote to keep s= upporting Java 7 for Flink 1.3 and
>>>>> then
>>>>>>>>> revisit
>>>>>>>>>>> once we are approaching 1.4 in= September.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Thu, Mar 16, 2017 a= t 8:00 AM, Bowen Li <
>>>>>>>> bowen.li@offerupnow.com
>>>>>>>>>>> <mailto:bowen.li@offerupnow.com>> wrote:
>>>>>>>>>>>>> There's always a t= radeoff we need to make. I'm in favor of
>>>>>>>> upgrading
>>>>>>>>>> to
>>>>>>>>>>> Java 8 to bring in all new Jav= a features.
>>>>>>>>>>>>>
>>>>>>>>>>>>> The common way I'v= e seen (and I agree) other software
>>>>> upgrading
>>>>>>>>> major
>>>>>>>>>>> things like this is 1) upgrade= for next big release without
>>>>>> backward
>>>>>>>>>>> compatibility and notify every= one 2) maintain and patch
>>>>> current,
>>>>>>>>> old-tech
>>>>>>>>>>> compatible version at a reason= ably limited scope. Building
>>>>>> backward
>>>>>>>>>>> compatibility is too much for = an open sourced project
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Wed, Mar 15, 2017 a= t 7:10 AM, Robert Metzger <
>>>>>>>>> rmetzger@apache.org
>>>>>>>>>>> <mailto:rmetzger@apache.org>> wrote:
>>>>>>>>>>>>> I've put it also o= n our Twitter account:
>>>>>>>>>>>>> https://twitter.com/ApacheFlink/status/84201506266775= 5521
>>>>> <
>>>>>>>>>>> https://twitter.com/ApacheFlink/status/842015062667755521&g= t;
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Wed, Mar 15, 2017 a= t 2:19 PM, Martin Neumann <
>>>>>>>>> martin.neumann@ri.se
>>>>>>>>>>> <mailto:martin.neumann@ri.se>>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> I think this easie= r done in a straw poll than in an
>>>>> email
>>>>>>>>>>> conversation.
>>>>>>>>>>>>>> I created one at: = http://www.strawpoll.me/12535073 <
>>>>>>>>>>> http://www.strawpoll.me= /12535073>
>>>>>>>>>>>>>> (Note that you hav= e multiple choices.)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Though I prefer Ja= va 8 most of the time I have to work
>>>>> on
>>>>>> Java
>>>>>>>> 7.
>>>>>>>>> A
>>>>>>>>>>> lot of
>>>>>>>>>>>>>> the infrastructure= I work on still runs Java 7, one of
>>>>> the
>>>>>>>>>> companies I
>>>>>>>>>>>>>> build a prototype = for a while back just updated to Java
>>>>> 7 2
>>>>>>>> years
>>>>>>>>>>> ago. I
>>>>>>>>>>>>>> doubt we can ditch= Java 7 support any time soon if we
>>>>> want to
>>>>>>>> make
>>>>>>>>>> it
>>>>>>>>>>> easy
>>>>>>>>>>>>>> for companies to u= se Flink.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> cheers Martin
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> //PS sorry if this= gets sent twice, we just migrated to
>>>>> a new
>>>>>>>> mail
>>>>>>>>>>> system
>>>>>>>>>>>>>> and a lot of thing= s are broken
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> __________________= ______________
>>>>>>>>>>>>>> From: Stephan Ewen= <sewen@apache.org <mailto: >>>>>> sewen@apache.o= rg
>>>>>>>>>>
>>>>>>>>>>>>>> Sent: Wednesday, M= arch 15, 2017 12:30:24 PM
>>>>>>>>>>>>>> To: user@flink.apache.org <mailto:user@flink.apache.org
>>>>>> ;
>>>>>>>>>>> dev@flink.apache.org <mailto:dev@flink.apache.org>
>>>>>>>>>>>>>> Subject: [POLL] Wh= o still uses Java 7 with Flink ?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi all!
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I would like to ge= t a feeling how much Java 7 is still
>>>>> being
>>>>>>>> used
>>>>>>>>>>> among
>>>>>>>>>>>>>> Flink users.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> At some point, it = would be great to drop Java 7 support
>>>>> and
>>>>>>>> make
>>>>>>>>> use
>>>>>>>>>>> of
>>>>>>>>>>>>>> Java 8's new f= eatures, but first we would need to get a
>>>>>> feeling
>>>>>>>>> how
>>>>>>>>>>> much
>>>>>>>>>>>>>> Java 7 is still us= ed.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Would be happy if = users on Java 7 respond here, or even
>>>>> users
>>>>>>>> that
>>>>>>>>>>> have
>>>>>>>>>>>>>> some insights into= how widespread they think Java 7
>>>>> still is.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>> Stephan
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>>
>>>
>>
>

--
Konstantin Knauf * konstant= in.knauf@tngtech.com * +49-174-3413182
TNG Technology Consulting GmbH, Betastr. 13a, 85774 Unterf=C3=B6hring
Gesch=C3=A4ftsf=C3=BChrer: Henrik Klagges, Christoph Stock, Dr. Robert Dahl= ke
Sitz: Unterf=C3=B6hring * Amtsgericht M=C3=BCnchen * HRB 135082

--001a11417a1ec6178e05542f840d--