Re: drop java 7 support for spark 2.1.x or spark 2.2.x

[Reynold Xin <rx...@databricks.com>]

Bumping this.

Given we see the occassional build breaks with Java 8, we should reconsider
this and do it for 2.2 or 2.3. By the time 2.2 is released, it will almost
be an year since this thread started.


On Sun, Jul 24, 2016 at 12:59 AM, Mark Hamstra <ma...@clearstorydata.com>
wrote:

> Sure, signalling well ahead of time is good, as is getting better
> performance from Java 8; but do either of those interests really require
> dropping Java 7 support sooner rather than later?
>
> Now, to retroactively copy edit myself, when I previously wrote "after
> all or nearly all relevant clusters are actually no longer running on Java
> 6", I meant "...no longer running on Java 7".  We should be at a point now
> where there aren't many Java 6 clusters left, but my sense is that there
> are still quite a number of Java 7 clusters around, and that there will be
> for a good while still.
>
> On Sat, Jul 23, 2016 at 3:50 PM, 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" <ma...@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
>>>
>>>
>>
>>
>

Re: drop java 7 support for spark 2.1.x or spark 2.2.x

[Reynold Xin <rx...@databricks.com>]

BTW I created a JIRA ticket for tracking:
https://issues.apache.org/jira/browse/SPARK-19493

We of course shouldn't do anything until we achieve consensus.


On Tue, Feb 7, 2017 at 3:47 PM, Reynold Xin <rx...@databricks.com> wrote:

> Bumping this.
>
> Given we see the occassional build breaks with Java 8, we should
> reconsider this and do it for 2.2 or 2.3. By the time 2.2 is released, it
> will almost be an year since this thread started.
>
>
> On Sun, Jul 24, 2016 at 12:59 AM, Mark Hamstra <ma...@clearstorydata.com>
> wrote:
>
>> Sure, signalling well ahead of time is good, as is getting better
>> performance from Java 8; but do either of those interests really require
>> dropping Java 7 support sooner rather than later?
>>
>> Now, to retroactively copy edit myself, when I previously wrote "after
>> all or nearly all relevant clusters are actually no longer running on Java
>> 6", I meant "...no longer running on Java 7".  We should be at a point now
>> where there aren't many Java 6 clusters left, but my sense is that there
>> are still quite a number of Java 7 clusters around, and that there will be
>> for a good while still.
>>
>> On Sat, Jul 23, 2016 at 3:50 PM, 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" <ma...@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
>>>>
>>>>
>>>
>>>
>>
>