BTW - "signalling ahead of time" is called deprecating, not dropping support... (personally I only use JDK 8 / Scala 2.11 so I'm for it)
Ofir Manor Co-Founder & CTO | Equalum Mobile: +972-54-7801286 | Email: ofir.ma...@equalum.io On Sun, Jul 24, 2016 at 1:50 AM, Koert Kuipers <ko...@tresata.com> wrote: > i care about signalling it in advance mostly. and given the performance > differences we do have some interest in pushing towards java 8 > > On Jul 23, 2016 6:10 PM, "Mark Hamstra" <m...@clearstorydata.com> wrote: > > Why the push to remove Java 7 support as soon as possible (which is how I > read your "cluster admins plan to migrate by date X, so Spark should end > Java 7 support then, too")? First, I don't think we should be removing > Java 7 support until some time after all or nearly all relevant clusters > are actually no longer running on Java 6, and that targeting removal of > support at our best guess about when admins are just *planning* to migrate > isn't a very good idea. Second, I don't see the significant difficulty or > harm in continuing to support Java 7 for a while longer. > > On Sat, Jul 23, 2016 at 2:54 PM, Koert Kuipers <ko...@tresata.com> wrote: > >> dropping java 7 support was considered for spark 2.0.x but we decided >> against it. >> >> ideally dropping support for a java version should be communicated far in >> advance to facilitate the transition. >> >> is this the right time to make that decision and start communicating it >> (mailing list, jira, etc.)? perhaps for spark 2.1.x or spark 2.2.x? >> >> my general sense is that most cluster admins have plans to migrate to >> java 8 before end of year. so that could line up nicely with spark 2.2 >> >> > >
