I don't think there's a target. The changes aren't all that hard (see the
SPARK-14220 umbrella) but there are some changes that are hard or
impossible without changing key APIs, as far as we can see. That would
suggest 3.0.

One motivation I have here for getting it as far as possible otherwise is
so people could, if they wanted, create a 2.12 build themselves without
much work even if it were not supported upstream. This particular change is
a lot of the miscellaneous stuff you'd have to fix to get to that point.

On Thu, Aug 31, 2017 at 11:04 AM Saisai Shao <sai.sai.s...@gmail.com> wrote:

> Hi Sean,
>
> Do we have a planned target version for Scala 2.12 support? Several other
> projects like Zeppelin, Livy which rely on Spark repl also require changes
> to support this Scala 2.12.
>
> Thanks
> Jerry
>
> On Thu, Aug 31, 2017 at 5:55 PM, Sean Owen <so...@cloudera.com> wrote:
>
>> No, this doesn't let Spark build and run on 2.12. It makes changes that
>> will be required though, the ones that are really no loss to the current
>> 2.11 build.
>>
>> On Thu, Aug 31, 2017, 10:48 Denis Bolshakov <bolshakov.de...@gmail.com>
>> wrote:
>>
>>> Hello,
>>>
>>> Sounds amazing. Is there any improvements in benchmarks?
>>>
>>>
>>> On 31 August 2017 at 12:25, Sean Owen <so...@cloudera.com> wrote:
>>>
>>>> Calling attention to the question of Scala 2.12 again for moment. I'd
>>>> like to make a modest step towards support. Have a look again, if you
>>>> would, at SPARK-14280:
>>>>
>>>> https://github.com/apache/spark/pull/18645
>>>>
>>>> This is a lot of the change for 2.12 that doesn't break 2.11, and
>>>> really doesn't add any complexity. It's mostly dependency updates and
>>>> clarifying some code. Other items like dealing with Kafka 0.8 support, the
>>>> 2.12 REPL, etc, are not  here.
>>>>
>>>> So, this still doesn't result in a working 2.12 build but it's most of
>>>> the miscellany that will be required.
>>>>
>>>> I'd like to merge it but wanted to flag it for feedback as it's not
>>>> trivial.
>>>>
>>>
>>>
>>>
>>> --
>>> //with Best Regards
>>> --Denis Bolshakov
>>> e-mail: bolshakov.de...@gmail.com
>>>
>>
>

Reply via email to