Thanks for the pointer. I am not sure whether Sebastian's concern regarding libraries is a big issue, as 2.11 code is backwards-compatible with the non-deprecated part of the stable 2.10 API [1]. The discussion is also 6 months old by now and a similar issue has been recently resolved in Spark [2].
It might be a good idea to keep this as a long-term goal and revisit it at some point in the next months. [1] http://www.scala-lang.org/news/2.11.0 [2] https://issues.apache.org/jira/browse/SPARK-4466 2015-01-15 18:01 GMT+01:00 Robert Metzger <rmetz...@apache.org>: > There has already been a discussion about this recently: > > http://apache-flink-incubator-mailing-list-archive.1008284.n3.nabble.com/Changing-Scala-Version-to-2-11-x-td1473.html > > On Thu, Jan 15, 2015 at 5:51 PM, Alexander Alexandrov < > alexander.s.alexand...@gmail.com> wrote: > > > Currently, Flink uses Scala 2.10.4 and relies on the macro paradise > > compiler plugin to get the quasi-quotes functionality. > > > > This makes the code incompatible with third-party add-ons that use macros > > written against a newer version of Scala. > > > > Scala 2.11 has been around for almost a year already. It comes with a bit > > more advanced reflection API than 2.10 and quasi-quotes bundled in. I > think > > that by now there should be a 2.11 version for most of the other > > Scala-based dependencies used in Flink. > > > > Are there any plans in the roadmap to upgrade this to 2.11 in one of the > > next releases? If not, what is the main issue blocking this change? > > > > I suspect that this might be a question which has been already discussed > > here, but I failed to find relevant threads in the mailing list. > > > > Regards, > > Alexander > > >
