I had favored this for 2.0 even, so favor it sooner than later. The general shape of the argument is:
- supporting Java 7 is starting to pinch a little because of extra builds and the inevitable gap between what the PR builder (7) tests and what the later Java 8 tests runs show - requiring Java 8 would allow a few minor cleanups in the code - Java 7 is already EOL (no, I don't count paying Oracle for support) but mostly importantly, - anyone can keep using 2.0 if they want to use Java 7. This does *not* require people to use Java 8. It requires them to use Java 8 to use the very latest version. On Sat, Jul 23, 2016 at 10: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 > --------------------------------------------------------------------- To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
