+1 to a move, the timeline seems reasonable to me. Agree we should find out more information from users next year before actually making the move to 8, but this is a good target.
On Mon, Dec 14, 2015 at 10:23 AM, Ryan Blue <[email protected]> wrote: > +1 for moving to Java 7 now. > > For Java 8, I think Dec 2016 sounds reasonable given the end of public > updates in April. But I think we should make that a goal and not a > commitment. Java 8 code can't be run on a Java 7 VM [1] and it may take > people a while to migrate even after free support runs out. > > I think it makes sense to see if we know about anyone running Java 7 mid > next year. > > rb > > > [1]: > https://stackoverflow.com/questions/16143684/can-java-8-code-be-compiled-to-run-on-java-7-jvm > > > On 12/12/2015 03:47 PM, Julien Le Dem wrote: > >> Parquet as a library has to move to new versions of java later to minimize >> pain on users. >> However it looks like it is high time to move to java 7 >> http://www.oracle.com/technetwork/java/eol-135779.html >> >> And we should probably define a deadline for java 7 support before moving >> to java 8. >> >> 2 questions: >> - any objection to moving parquet to java 7? >> - let's define a date for moving to java 8 so that users have time to >> plan >> ahead or argue against. I propose Dec 2016. Any other proposal? >> >> Related PR: >> https://github.com/apache/parquet-mr/pull/231 >> >> > > -- > Ryan Blue > Software Engineer > Cloudera, Inc. >
