[DISCUSS] Drop Scala 2.11
Locked
 
|
Hi Everyone,
Think of this as a pre-flip, but what does everyone think about dropping Scala 2.11 support from Flink. The last patch release was in 2017 and in that time the scala community has released 2.13 and is working towards a 3.0 release. Apache Kafka and Spark have both dropped 2.11 support in recent versions. In fact, Flink's universal Kafka connector is stuck on 2.4 because that is the last version with scala 2.11 support. What are people's thoughts on dropping Scala 2.11? How many are still using it in production? Seth |
|
|
I'd be fine with dropping Scala 2.11. Stateful Functions currently requires
2.11, though, so that would have to be addressed as well. I'm using 2.11 in a production project now but only because of the Stateful Functions dependency. If I could use a newer Scala version that would be fine/preferred. On Thu, Sep 10, 2020 at 10:52 AM Seth Wiesman <[hidden email]> wrote: > Hi Everyone, > > Think of this as a pre-flip, but what does everyone think about dropping > Scala 2.11 support from Flink. > > The last patch release was in 2017 and in that time the scala community has > released 2.13 and is working towards a 3.0 release. Apache Kafka and Spark > have both dropped 2.11 support in recent versions. In fact, Flink's > universal Kafka connector is stuck on 2.4 because that is the last version > with scala 2.11 support. > > What are people's thoughts on dropping Scala 2.11? How many are still using > it in production? > > Seth > |
Re: [DISCUSS] Drop Scala 2.11
|
|
In reply to this post by Seth Wiesman-4
Yes! I would be in favour of this since it's blocking us from upgrading
certain dependencies. I would also be in favour of dropping Scala completely but that's a different story. Aljoscha On 10.09.20 16:51, Seth Wiesman wrote: > Hi Everyone, > > Think of this as a pre-flip, but what does everyone think about dropping > Scala 2.11 support from Flink. > > The last patch release was in 2017 and in that time the scala community has > released 2.13 and is working towards a 3.0 release. Apache Kafka and Spark > have both dropped 2.11 support in recent versions. In fact, Flink's > universal Kafka connector is stuck on 2.4 because that is the last version > with scala 2.11 support. > > What are people's thoughts on dropping Scala 2.11? How many are still using > it in production? > > Seth > |
Re: [DISCUSS] Drop Scala 2.11
|
|
That makes sense.
We are using 2.12 for our production Also, for flink scala 2.12 support, it is in fact limited to scala 2.12.7. It is binary incompatible with version 2.12 above ( https://issues.apache.org/jira/browse/FLINK-12461 ) That would be great to at least move to a more recent 2.12 version, and ideally to 2.13. Is there any scala support plan available? Matthieu On Thu, Sep 10, 2020 at 5:00 PM Aljoscha Krettek <[hidden email]> wrote: > Yes! I would be in favour of this since it's blocking us from upgrading > certain dependencies. > > I would also be in favour of dropping Scala completely but that's a > different story. > > Aljoscha > > On 10.09.20 16:51, Seth Wiesman wrote: > > Hi Everyone, > > > > Think of this as a pre-flip, but what does everyone think about dropping > > Scala 2.11 support from Flink. > > > > The last patch release was in 2017 and in that time the scala community > has > > released 2.13 and is working towards a 3.0 release. Apache Kafka and > Spark > > have both dropped 2.11 support in recent versions. In fact, Flink's > > universal Kafka connector is stuck on 2.4 because that is the last > version > > with scala 2.11 support. > > > > What are people's thoughts on dropping Scala 2.11? How many are still > using > > it in production? > > > > Seth > > > > -- Matthieu Bonneviot Senior R&D Engineer, DataDome M +33 7 68 29 79 34 <+33+7+68+29+79+34> E [hidden email] <[hidden email]> W www.datadome.co <http://www.datadome.co?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature> [image: facebook] <https://www.facebook.com/datadome/?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature> [image: linkedin] <https://fr.linkedin.com/company/datadome?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature> [image: twitter] <https://twitter.com/data_dome?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature> |
|
|
@glen
Yes, we would absolutely migrate statefun. StateFun can be compiled with Scala 2.12 today, I'm not sure why it's not cross released. @aljoscha :) @mathieu Its on the roadmap but it's non-trivial and I'm not aware of anyone actively working on it. On Thu, Sep 10, 2020 at 10:09 AM Matthieu Bonneviot <[hidden email]> wrote: > That makes sense. > We are using 2.12 for our production > Also, for flink scala 2.12 support, it is in fact limited to scala 2.12.7. > It is binary incompatible with version 2.12 above ( > https://issues.apache.org/jira/browse/FLINK-12461 ) > That would be great to at least move to a more recent 2.12 version, and > ideally to 2.13. > > Is there any scala support plan available? > > Matthieu > > > On Thu, Sep 10, 2020 at 5:00 PM Aljoscha Krettek <[hidden email]> > wrote: > > > Yes! I would be in favour of this since it's blocking us from upgrading > > certain dependencies. > > > > I would also be in favour of dropping Scala completely but that's a > > different story. > > > > Aljoscha > > > > On 10.09.20 16:51, Seth Wiesman wrote: > > > Hi Everyone, > > > > > > Think of this as a pre-flip, but what does everyone think about > dropping > > > Scala 2.11 support from Flink. > > > > > > The last patch release was in 2017 and in that time the scala community > > has > > > released 2.13 and is working towards a 3.0 release. Apache Kafka and > > Spark > > > have both dropped 2.11 support in recent versions. In fact, Flink's > > > universal Kafka connector is stuck on 2.4 because that is the last > > version > > > with scala 2.11 support. > > > > > > What are people's thoughts on dropping Scala 2.11? How many are still > > using > > > it in production? > > > > > > Seth > > > > > > > > > -- > Matthieu Bonneviot > Senior R&D Engineer, DataDome > M +33 7 68 29 79 34 <+33+7+68+29+79+34> > E [hidden email] <[hidden email]> > W www.datadome.co > < > http://www.datadome.co?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature > > > > [image: facebook] > < > https://www.facebook.com/datadome/?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature > > > [image: > linkedin] > < > https://fr.linkedin.com/company/datadome?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature > > > [image: > twitter] > < > https://twitter.com/data_dome?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature > > > |
|
|
@Galen FYI: the upcoming StateFun release would use Scala2.12
On Thu, Sep 10, 2020 at 5:14 PM Seth Wiesman <[hidden email]> wrote: > @glen > > Yes, we would absolutely migrate statefun. StateFun can be compiled with > Scala 2.12 today, I'm not sure why it's not cross released. > > @aljoscha :) > > @mathieu Its on the roadmap but it's non-trivial and I'm not aware of > anyone actively working on it. > > On Thu, Sep 10, 2020 at 10:09 AM Matthieu Bonneviot > <[hidden email]> wrote: > >> That makes sense. >> We are using 2.12 for our production >> Also, for flink scala 2.12 support, it is in fact limited to scala 2.12.7. >> It is binary incompatible with version 2.12 above ( >> https://issues.apache.org/jira/browse/FLINK-12461 ) >> That would be great to at least move to a more recent 2.12 version, and >> ideally to 2.13. >> >> Is there any scala support plan available? >> >> Matthieu >> >> >> On Thu, Sep 10, 2020 at 5:00 PM Aljoscha Krettek <[hidden email]> >> wrote: >> >> > Yes! I would be in favour of this since it's blocking us from upgrading >> > certain dependencies. >> > >> > I would also be in favour of dropping Scala completely but that's a >> > different story. >> > >> > Aljoscha >> > >> > On 10.09.20 16:51, Seth Wiesman wrote: >> > > Hi Everyone, >> > > >> > > Think of this as a pre-flip, but what does everyone think about >> dropping >> > > Scala 2.11 support from Flink. >> > > >> > > The last patch release was in 2017 and in that time the scala >> community >> > has >> > > released 2.13 and is working towards a 3.0 release. Apache Kafka and >> > Spark >> > > have both dropped 2.11 support in recent versions. In fact, Flink's >> > > universal Kafka connector is stuck on 2.4 because that is the last >> > version >> > > with scala 2.11 support. >> > > >> > > What are people's thoughts on dropping Scala 2.11? How many are still >> > using >> > > it in production? >> > > >> > > Seth >> > > >> > >> > >> >> -- >> Matthieu Bonneviot >> Senior R&D Engineer, DataDome >> M +33 7 68 29 79 34 <+33+7+68+29+79+34> >> E [hidden email] <[hidden email]> >> W www.datadome.co >> < >> http://www.datadome.co?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature >> > >> >> [image: facebook] >> < >> https://www.facebook.com/datadome/?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature >> > >> [image: >> linkedin] >> < >> https://fr.linkedin.com/company/datadome?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature >> > >> [image: >> twitter] >> < >> https://twitter.com/data_dome?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature >> > >> > |
|
|
Big +1 to drop Scala 2.11
This would mean that we can finally use Java 8 language features that are integrated with Scala. Regards, Timo On 11.09.20 13:15, Igal Shilman wrote: > @Galen FYI: the upcoming StateFun release would use Scala2.12 > > On Thu, Sep 10, 2020 at 5:14 PM Seth Wiesman <[hidden email]> wrote: > >> @glen >> >> Yes, we would absolutely migrate statefun. StateFun can be compiled with >> Scala 2.12 today, I'm not sure why it's not cross released. >> >> @aljoscha :) >> >> @mathieu Its on the roadmap but it's non-trivial and I'm not aware of >> anyone actively working on it. >> >> On Thu, Sep 10, 2020 at 10:09 AM Matthieu Bonneviot >> <[hidden email]> wrote: >> >>> That makes sense. >>> We are using 2.12 for our production >>> Also, for flink scala 2.12 support, it is in fact limited to scala 2.12.7. >>> It is binary incompatible with version 2.12 above ( >>> https://issues.apache.org/jira/browse/FLINK-12461 ) >>> That would be great to at least move to a more recent 2.12 version, and >>> ideally to 2.13. >>> >>> Is there any scala support plan available? >>> >>> Matthieu >>> >>> >>> On Thu, Sep 10, 2020 at 5:00 PM Aljoscha Krettek <[hidden email]> >>> wrote: >>> >>>> Yes! I would be in favour of this since it's blocking us from upgrading >>>> certain dependencies. >>>> >>>> I would also be in favour of dropping Scala completely but that's a >>>> different story. >>>> >>>> Aljoscha >>>> >>>> On 10.09.20 16:51, Seth Wiesman wrote: >>>>> Hi Everyone, >>>>> >>>>> Think of this as a pre-flip, but what does everyone think about >>> dropping >>>>> Scala 2.11 support from Flink. >>>>> >>>>> The last patch release was in 2017 and in that time the scala >>> community >>>> has >>>>> released 2.13 and is working towards a 3.0 release. Apache Kafka and >>>> Spark >>>>> have both dropped 2.11 support in recent versions. In fact, Flink's >>>>> universal Kafka connector is stuck on 2.4 because that is the last >>>> version >>>>> with scala 2.11 support. >>>>> >>>>> What are people's thoughts on dropping Scala 2.11? How many are still >>>> using >>>>> it in production? >>>>> >>>>> Seth >>>>> >>>> >>>> >>> >>> -- >>> Matthieu Bonneviot >>> Senior R&D Engineer, DataDome >>> M +33 7 68 29 79 34 <+33+7+68+29+79+34> >>> E [hidden email] <[hidden email]> >>> W www.datadome.co >>> < >>> http://www.datadome.co?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature >>>> >>> >>> [image: facebook] >>> < >>> https://www.facebook.com/datadome/?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature >>>> >>> [image: >>> linkedin] >>> < >>> https://fr.linkedin.com/company/datadome?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature >>>> >>> [image: >>> twitter] >>> < >>> https://twitter.com/data_dome?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature >>>> >>> >> > |
Re: [DISCUSS] Drop Scala 2.11
|
|
Are we then also dropping the scala-shell, since it still doesn't work
on 2.12? On 9/11/2020 2:12 PM, Timo Walther wrote: > Big +1 to drop Scala 2.11 > > This would mean that we can finally use Java 8 language features that > are integrated with Scala. > > Regards, > Timo > > On 11.09.20 13:15, Igal Shilman wrote: >> @Galen FYI: the upcoming StateFun release would use Scala2.12 >> >> On Thu, Sep 10, 2020 at 5:14 PM Seth Wiesman <[hidden email]> >> wrote: >> >>> @glen >>> >>> Yes, we would absolutely migrate statefun. StateFun can be compiled >>> with >>> Scala 2.12 today, I'm not sure why it's not cross released. >>> >>> @aljoscha :) >>> >>> @mathieu Its on the roadmap but it's non-trivial and I'm not aware of >>> anyone actively working on it. >>> >>> On Thu, Sep 10, 2020 at 10:09 AM Matthieu Bonneviot >>> <[hidden email]> wrote: >>> >>>> That makes sense. >>>> We are using 2.12 for our production >>>> Also, for flink scala 2.12 support, it is in fact limited to scala >>>> 2.12.7. >>>> It is binary incompatible with version 2.12 above ( >>>> https://issues.apache.org/jira/browse/FLINK-12461 ) >>>> That would be great to at least move to a more recent 2.12 version, >>>> and >>>> ideally to 2.13. >>>> >>>> Is there any scala support plan available? >>>> >>>> Matthieu >>>> >>>> >>>> On Thu, Sep 10, 2020 at 5:00 PM Aljoscha Krettek <[hidden email]> >>>> wrote: >>>> >>>>> Yes! I would be in favour of this since it's blocking us from >>>>> upgrading >>>>> certain dependencies. >>>>> >>>>> I would also be in favour of dropping Scala completely but that's a >>>>> different story. >>>>> >>>>> Aljoscha >>>>> >>>>> On 10.09.20 16:51, Seth Wiesman wrote: >>>>>> Hi Everyone, >>>>>> >>>>>> Think of this as a pre-flip, but what does everyone think about >>>> dropping >>>>>> Scala 2.11 support from Flink. >>>>>> >>>>>> The last patch release was in 2017 and in that time the scala >>>> community >>>>> has >>>>>> released 2.13 and is working towards a 3.0 release. Apache Kafka and >>>>> Spark >>>>>> have both dropped 2.11 support in recent versions. In fact, Flink's >>>>>> universal Kafka connector is stuck on 2.4 because that is the last >>>>> version >>>>>> with scala 2.11 support. >>>>>> >>>>>> What are people's thoughts on dropping Scala 2.11? How many are >>>>>> still >>>>> using >>>>>> it in production? >>>>>> >>>>>> Seth >>>>>> >>>>> >>>>> >>>> >>>> -- >>>> Matthieu Bonneviot >>>> Senior R&D Engineer, DataDome >>>> M +33 7 68 29 79 34 <+33+7+68+29+79+34> >>>> E [hidden email] <[hidden email]> >>>> W www.datadome.co >>>> < >>>> http://www.datadome.co?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature >>>> >>>>> >>>> >>>> [image: facebook] >>>> < >>>> https://www.facebook.com/datadome/?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature >>>> >>>>> >>>> [image: >>>> linkedin] >>>> < >>>> https://fr.linkedin.com/company/datadome?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature >>>> >>>>> >>>> [image: >>>> twitter] >>>> < >>>> https://twitter.com/data_dome?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature >>>> >>>>> >>>> >>> >> > > |
|
|
I would hope we can make scala shell with scala 2.12 before dropping 2.11,
many users are still using scala shell to try out new features of flink, especially for new users. Chesnay Schepler <[hidden email]> 于2020年9月13日周日 下午7:59写道： > Are we then also dropping the scala-shell, since it still doesn't work > on 2.12? > > On 9/11/2020 2:12 PM, Timo Walther wrote: > > Big +1 to drop Scala 2.11 > > > > This would mean that we can finally use Java 8 language features that > > are integrated with Scala. > > > > Regards, > > Timo > > > > On 11.09.20 13:15, Igal Shilman wrote: > >> @Galen FYI: the upcoming StateFun release would use Scala2.12 > >> > >> On Thu, Sep 10, 2020 at 5:14 PM Seth Wiesman <[hidden email]> > >> wrote: > >> > >>> @glen > >>> > >>> Yes, we would absolutely migrate statefun. StateFun can be compiled > >>> with > >>> Scala 2.12 today, I'm not sure why it's not cross released. > >>> > >>> @aljoscha :) > >>> > >>> @mathieu Its on the roadmap but it's non-trivial and I'm not aware of > >>> anyone actively working on it. > >>> > >>> On Thu, Sep 10, 2020 at 10:09 AM Matthieu Bonneviot > >>> <[hidden email]> wrote: > >>> > >>>> That makes sense. > >>>> We are using 2.12 for our production > >>>> Also, for flink scala 2.12 support, it is in fact limited to scala > >>>> 2.12.7. > >>>> It is binary incompatible with version 2.12 above ( > >>>> https://issues.apache.org/jira/browse/FLINK-12461 ) > >>>> That would be great to at least move to a more recent 2.12 version, > >>>> and > >>>> ideally to 2.13. > >>>> > >>>> Is there any scala support plan available? > >>>> > >>>> Matthieu > >>>> > >>>> > >>>> On Thu, Sep 10, 2020 at 5:00 PM Aljoscha Krettek <[hidden email] > > > >>>> wrote: > >>>> > >>>>> Yes! I would be in favour of this since it's blocking us from > >>>>> upgrading > >>>>> certain dependencies. > >>>>> > >>>>> I would also be in favour of dropping Scala completely but that's a > >>>>> different story. > >>>>> > >>>>> Aljoscha > >>>>> > >>>>> On 10.09.20 16:51, Seth Wiesman wrote: > >>>>>> Hi Everyone, > >>>>>> > >>>>>> Think of this as a pre-flip, but what does everyone think about > >>>> dropping > >>>>>> Scala 2.11 support from Flink. > >>>>>> > >>>>>> The last patch release was in 2017 and in that time the scala > >>>> community > >>>>> has > >>>>>> released 2.13 and is working towards a 3.0 release. Apache Kafka and > >>>>> Spark > >>>>>> have both dropped 2.11 support in recent versions. In fact, Flink's > >>>>>> universal Kafka connector is stuck on 2.4 because that is the last > >>>>> version > >>>>>> with scala 2.11 support. > >>>>>> > >>>>>> What are people's thoughts on dropping Scala 2.11? How many are > >>>>>> still > >>>>> using > >>>>>> it in production? > >>>>>> > >>>>>> Seth > >>>>>> > >>>>> > >>>>> > >>>> > >>>> -- > >>>> Matthieu Bonneviot > >>>> Senior R&D Engineer, DataDome > >>>> M +33 7 68 29 79 34 <+33+7+68+29+79+34> > >>>> E [hidden email] <[hidden email]> > >>>> W www.datadome.co > >>>> < > >>>> > http://www.datadome.co?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature > >>>> > >>>>> > >>>> > >>>> [image: facebook] > >>>> < > >>>> > https://www.facebook.com/datadome/?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature > >>>> > >>>>> > >>>> [image: > >>>> linkedin] > >>>> < > >>>> > https://fr.linkedin.com/company/datadome?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature > >>>> > >>>>> > >>>> [image: > >>>> twitter] > >>>> < > >>>> > https://twitter.com/data_dome?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature > >>>> > >>>>> > >>>> > >>> > >> > > > > > > -- Best Regards Jeff Zhang |
Re: [DISCUSS] Drop Scala 2.11
|
|
In reply to this post by Igal Shilman
We use a Cloudera 6.3 cluster in prod. I'd guess that it's still widely used in prod as those cloudera upgrades for major versions are planned long time ahead and take a significant amount of resources in big data lakes.
On that 6.3. cluster, if I open spark-shell, I still see scala 2.11 in use: > Using Scala version 2.11.12 (Java HotSpot(TM) 64-Bit Server VM, Java 1.8.0_181) Just to don't mess with any dependencies and as we have both, Flink and Spark jobs, we declare all dependencies with scala_2.11. But we never actually tried what happens if we would change that. We just seek maximum compatibility while at the same time, maintain and upgrade Flink ourselves to keep up with the development pace of the fast community and being able to use the latest major version quickly. So my suggestion: As long as it isn't much pain, I'd like to keep the scala 2.11 support for a while. (or even better for me as a Java, but never scala developer: Drop it completely :) ) Speaking for my project: I think our ops team plans to upgrade to Cloudera 7 somewhere around Q2 2021, so personally I'm fine with dropping it then. Best regards Theo Von: "Igal Shilman" <[hidden email]> An: "Seth Wiesman" <[hidden email]> CC: "dev" <[hidden email]>, "user" <[hidden email]> Gesendet: Freitag, 11. September 2020 13:15:38 Betreff: Re: [DISCUSS] Drop Scala 2.11 @Galen FYI: the upcoming StateFun release would use Scala2.12 On Thu, Sep 10, 2020 at 5:14 PM Seth Wiesman < [ mailto:[hidden email] | [hidden email] ] > wrote: @glen Yes, we would absolutely migrate statefun. StateFun can be compiled with Scala 2.12 today, I'm not sure why it's not cross released. @aljoscha :) @mathieu Its on the roadmap but it's non-trivial and I'm not aware of anyone actively working on it. On Thu, Sep 10, 2020 at 10:09 AM Matthieu Bonneviot <[hidden email]> wrote: BQ_BEGIN That makes sense. We are using 2.12 for our production Also, for flink scala 2.12 support, it is in fact limited to scala 2.12.7. It is binary incompatible with version 2.12 above ( [ https://issues.apache.org/jira/browse/FLINK-12461 | https://issues.apache.org/jira/browse/FLINK-12461 ] ) That would be great to at least move to a more recent 2.12 version, and ideally to 2.13. Is there any scala support plan available? Matthieu On Thu, Sep 10, 2020 at 5:00 PM Aljoscha Krettek < [ mailto:[hidden email] | [hidden email] ] > wrote: > Yes! I would be in favour of this since it's blocking us from upgrading > certain dependencies. > > I would also be in favour of dropping Scala completely but that's a > different story. > > Aljoscha > > On 10.09.20 16:51, Seth Wiesman wrote: > > Hi Everyone, > > > > Think of this as a pre-flip, but what does everyone think about dropping > > Scala 2.11 support from Flink. > > > > The last patch release was in 2017 and in that time the scala community > has > > released 2.13 and is working towards a 3.0 release. Apache Kafka and > Spark > > have both dropped 2.11 support in recent versions. In fact, Flink's > > universal Kafka connector is stuck on 2.4 because that is the last > version > > with scala 2.11 support. > > > > What are people's thoughts on dropping Scala 2.11? How many are still > using > > it in production? > > > > Seth > > > > -- Matthieu Bonneviot Senior R&D Engineer, DataDome M +33 7 68 29 79 34 <+33+7+68+29+79+34> E [ mailto:[hidden email] | [hidden email] ] < [ mailto:[hidden email] | [hidden email] ] > W [ http://www.datadome.co/ | www.datadome.co ] < [ http://www.datadome.co/?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature | http://www.datadome.co?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature ] > [image: facebook] < [ https://www.facebook.com/datadome/?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature | https://www.facebook.com/datadome/?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature ] > [image: linkedin] < [ https://fr.linkedin.com/company/datadome?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature | https://fr.linkedin.com/company/datadome?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature ] > [image: twitter] < [ https://twitter.com/data_dome?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature | https://twitter.com/data_dome?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature ] > BQ_END |
Re: [DISCUSS] Drop Scala 2.11
|
|
In reply to this post by Jeff Zhang
There is some new enthusiasm for bringing Scala 2.13 support to Flink:
https://issues.apache.org/jira/browse/FLINK-13414. One of the assumed prerequisites for this is dropping support for Scala 2.11 because it will be too hard (impossible) to try and support three Scala versions at the same time. What do you all think now that some time has passed? I would still be in favour of dropping Scala 2.11 but I can see Theo's point of people being tied to distro releases. On the other hand, Scala 2.11 is quite old now and some projects (such as Kafka) don't release newer versions with Scala 2.11 support. Best, Aljoscha On 2020/09/13 21:48, Jeff Zhang wrote: >I would hope we can make scala shell with scala 2.12 before dropping 2.11, >many users are still using scala shell to try out new features of flink, >especially for new users. > > >Chesnay Schepler <[hidden email]> 于2020年9月13日周日 下午7:59写道： > >> Are we then also dropping the scala-shell, since it still doesn't work >> on 2.12? >> >> On 9/11/2020 2:12 PM, Timo Walther wrote: >> > Big +1 to drop Scala 2.11 >> > >> > This would mean that we can finally use Java 8 language features that >> > are integrated with Scala. >> > >> > Regards, >> > Timo >> > >> > On 11.09.20 13:15, Igal Shilman wrote: >> >> @Galen FYI: the upcoming StateFun release would use Scala2.12 >> >> >> >> On Thu, Sep 10, 2020 at 5:14 PM Seth Wiesman <[hidden email]> >> >> wrote: >> >> >> >>> @glen >> >>> >> >>> Yes, we would absolutely migrate statefun. StateFun can be compiled >> >>> with >> >>> Scala 2.12 today, I'm not sure why it's not cross released. >> >>> >> >>> @aljoscha :) >> >>> >> >>> @mathieu Its on the roadmap but it's non-trivial and I'm not aware of >> >>> anyone actively working on it. >> >>> >> >>> On Thu, Sep 10, 2020 at 10:09 AM Matthieu Bonneviot >> >>> <[hidden email]> wrote: >> >>> >> >>>> That makes sense. >> >>>> We are using 2.12 for our production >> >>>> Also, for flink scala 2.12 support, it is in fact limited to scala >> >>>> 2.12.7. >> >>>> It is binary incompatible with version 2.12 above ( >> >>>> https://issues.apache.org/jira/browse/FLINK-12461 ) >> >>>> That would be great to at least move to a more recent 2.12 version, >> >>>> and >> >>>> ideally to 2.13. >> >>>> >> >>>> Is there any scala support plan available? >> >>>> >> >>>> Matthieu >> >>>> >> >>>> >> >>>> On Thu, Sep 10, 2020 at 5:00 PM Aljoscha Krettek <[hidden email] >> > >> >>>> wrote: >> >>>> >> >>>>> Yes! I would be in favour of this since it's blocking us from >> >>>>> upgrading >> >>>>> certain dependencies. >> >>>>> >> >>>>> I would also be in favour of dropping Scala completely but that's a >> >>>>> different story. >> >>>>> >> >>>>> Aljoscha >> >>>>> >> >>>>> On 10.09.20 16:51, Seth Wiesman wrote: >> >>>>>> Hi Everyone, >> >>>>>> >> >>>>>> Think of this as a pre-flip, but what does everyone think about >> >>>> dropping >> >>>>>> Scala 2.11 support from Flink. >> >>>>>> >> >>>>>> The last patch release was in 2017 and in that time the scala >> >>>> community >> >>>>> has >> >>>>>> released 2.13 and is working towards a 3.0 release. Apache Kafka and >> >>>>> Spark >> >>>>>> have both dropped 2.11 support in recent versions. In fact, Flink's >> >>>>>> universal Kafka connector is stuck on 2.4 because that is the last >> >>>>> version >> >>>>>> with scala 2.11 support. >> >>>>>> >> >>>>>> What are people's thoughts on dropping Scala 2.11? How many are >> >>>>>> still >> >>>>> using >> >>>>>> it in production? >> >>>>>> >> >>>>>> Seth >> >>>>>> >> >>>>> >> >>>>> >> >>>> >> >>>> -- >> >>>> Matthieu Bonneviot >> >>>> Senior R&D Engineer, DataDome >> >>>> M +33 7 68 29 79 34 <+33+7+68+29+79+34> >> >>>> E [hidden email] <[hidden email]> >> >>>> W www.datadome.co >> >>>> < >> >>>> >> http://www.datadome.co?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature >> >>>> >> >>>>> >> >>>> >> >>>> [image: facebook] >> >>>> < >> >>>> >> https://www.facebook.com/datadome/?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature >> >>>> >> >>>>> >> >>>> [image: >> >>>> linkedin] >> >>>> < >> >>>> >> https://fr.linkedin.com/company/datadome?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature >> >>>> >> >>>>> >> >>>> [image: >> >>>> twitter] >> >>>> < >> >>>> >> https://twitter.com/data_dome?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature >> >>>> >> >>>>> >> >>>> >> >>> >> >> >> > >> > >> >> > >-- >Best Regards > >Jeff Zhang |
|
|
Glad to see someone in community would like to drive this effort.
If scala 2.13 can do whatever scala 2.11 can do in flink (such as support scala-shell, scala lambda udf and etc), then I would be 100% support of dropping scala 2.11. Aljoscha Krettek <[hidden email]> 于2021年1月5日周二 下午11:01写道： > There is some new enthusiasm for bringing Scala 2.13 support to Flink: > https://issues.apache.org/jira/browse/FLINK-13414. > > One of the assumed prerequisites for this is dropping support for Scala > 2.11 because it will be too hard (impossible) to try and support three > Scala versions at the same time. > > What do you all think now that some time has passed? > > I would still be in favour of dropping Scala 2.11 but I can see Theo's > point of people being tied to distro releases. On the other hand, Scala > 2.11 is quite old now and some projects (such as Kafka) don't release > newer versions with Scala 2.11 support. > > Best, > Aljoscha > > On 2020/09/13 21:48, Jeff Zhang wrote: > >I would hope we can make scala shell with scala 2.12 before dropping 2.11, > >many users are still using scala shell to try out new features of flink, > >especially for new users. > > > > > >Chesnay Schepler <[hidden email]> 于2020年9月13日周日 下午7:59写道： > > > >> Are we then also dropping the scala-shell, since it still doesn't work > >> on 2.12? > >> > >> On 9/11/2020 2:12 PM, Timo Walther wrote: > >> > Big +1 to drop Scala 2.11 > >> > > >> > This would mean that we can finally use Java 8 language features that > >> > are integrated with Scala. > >> > > >> > Regards, > >> > Timo > >> > > >> > On 11.09.20 13:15, Igal Shilman wrote: > >> >> @Galen FYI: the upcoming StateFun release would use Scala2.12 > >> >> > >> >> On Thu, Sep 10, 2020 at 5:14 PM Seth Wiesman <[hidden email]> > >> >> wrote: > >> >> > >> >>> @glen > >> >>> > >> >>> Yes, we would absolutely migrate statefun. StateFun can be compiled > >> >>> with > >> >>> Scala 2.12 today, I'm not sure why it's not cross released. > >> >>> > >> >>> @aljoscha :) > >> >>> > >> >>> @mathieu Its on the roadmap but it's non-trivial and I'm not aware > of > >> >>> anyone actively working on it. > >> >>> > >> >>> On Thu, Sep 10, 2020 at 10:09 AM Matthieu Bonneviot > >> >>> <[hidden email]> wrote: > >> >>> > >> >>>> That makes sense. > >> >>>> We are using 2.12 for our production > >> >>>> Also, for flink scala 2.12 support, it is in fact limited to scala > >> >>>> 2.12.7. > >> >>>> It is binary incompatible with version 2.12 above ( > >> >>>> https://issues.apache.org/jira/browse/FLINK-12461 ) > >> >>>> That would be great to at least move to a more recent 2.12 version, > >> >>>> and > >> >>>> ideally to 2.13. > >> >>>> > >> >>>> Is there any scala support plan available? > >> >>>> > >> >>>> Matthieu > >> >>>> > >> >>>> > >> >>>> On Thu, Sep 10, 2020 at 5:00 PM Aljoscha Krettek < > [hidden email] > >> > > >> >>>> wrote: > >> >>>> > >> >>>>> Yes! I would be in favour of this since it's blocking us from > >> >>>>> upgrading > >> >>>>> certain dependencies. > >> >>>>> > >> >>>>> I would also be in favour of dropping Scala completely but that's > a > >> >>>>> different story. > >> >>>>> > >> >>>>> Aljoscha > >> >>>>> > >> >>>>> On 10.09.20 16:51, Seth Wiesman wrote: > >> >>>>>> Hi Everyone, > >> >>>>>> > >> >>>>>> Think of this as a pre-flip, but what does everyone think about > >> >>>> dropping > >> >>>>>> Scala 2.11 support from Flink. > >> >>>>>> > >> >>>>>> The last patch release was in 2017 and in that time the scala > >> >>>> community > >> >>>>> has > >> >>>>>> released 2.13 and is working towards a 3.0 release. Apache Kafka > and > >> >>>>> Spark > >> >>>>>> have both dropped 2.11 support in recent versions. In fact, > Flink's > >> >>>>>> universal Kafka connector is stuck on 2.4 because that is the > last > >> >>>>> version > >> >>>>>> with scala 2.11 support. > >> >>>>>> > >> >>>>>> What are people's thoughts on dropping Scala 2.11? How many are > >> >>>>>> still > >> >>>>> using > >> >>>>>> it in production? > >> >>>>>> > >> >>>>>> Seth > >> >>>>>> > >> >>>>> > >> >>>>> > >> >>>> > >> >>>> -- > >> >>>> Matthieu Bonneviot > >> >>>> Senior R&D Engineer, DataDome > >> >>>> M +33 7 68 29 79 34 <+33+7+68+29+79+34> > >> >>>> E [hidden email] <[hidden email]> > >> >>>> W www.datadome.co > >> >>>> < > >> >>>> > >> > http://www.datadome.co?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature > >> >>>> > >> >>>>> > >> >>>> > >> >>>> [image: facebook] > >> >>>> < > >> >>>> > >> > https://www.facebook.com/datadome/?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature > >> >>>> > >> >>>>> > >> >>>> [image: > >> >>>> linkedin] > >> >>>> < > >> >>>> > >> > https://fr.linkedin.com/company/datadome?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature > >> >>>> > >> >>>>> > >> >>>> [image: > >> >>>> twitter] > >> >>>> < > >> >>>> > >> > https://twitter.com/data_dome?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature > >> >>>> > >> >>>>> > >> >>>> > >> >>> > >> >> > >> > > >> > > >> > >> > > > >-- > >Best Regards > > > >Jeff Zhang > -- Best Regards Jeff Zhang |
«
Return to (DEPRECATED) Apache Flink Mailing List archive.
|
1 view|%1 views
| Free forum by Nabble | Edit this page |