Github user DieBauer commented on the issue:
https://github.com/apache/flink/pull/3703
Hi, I'm sorry for the late reaction. I haven't found the time to work on
this anymore (also priorities shifted... )
Therefore this pull request is stale. (it still could be used as a
Github user aljoscha commented on the issue:
https://github.com/apache/flink/pull/3703
@DieBauer Do you still wan't to work on this? I also started trying to make
Flink ready for 2.12 before I noticed this older branch. I'd be very happy to
stop, though, if you're interested in
Github user joan38 commented on the issue:
https://github.com/apache/flink/pull/3703
So I guess this PR is abandoned?
---
Github user joan38 commented on the issue:
https://github.com/apache/flink/pull/3703
Is there any news on this?
---
Github user ariskk commented on the issue:
https://github.com/apache/flink/pull/3703
We are really looking forward to this ð
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user joan38 commented on the issue:
https://github.com/apache/flink/pull/3703
@greghogan That's a pretty good news.
Thanks for your answer.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user greghogan commented on the issue:
https://github.com/apache/flink/pull/3703
@joan38 there has been a discussion on the mailing list about dropping Java
7 support (no one has objected) which will make it simpler to support Scala
2.12 in the upcoming release.
---
If your
Github user joan38 commented on the issue:
https://github.com/apache/flink/pull/3703
Any news on this?
2.13.0-M1 is out https://github.com/scala/scala/releases/tag/v2.13.0-M1
I'm wondering if we will still be on 2.11 when 2,13,0 is out.
---
If your project is set up for it,
Github user fhueske commented on the issue:
https://github.com/apache/flink/pull/3703
@frankbohman just watch the JIRA issue:
https://issues.apache.org/jira/browse/FLINK-5005
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user frankbohman commented on the issue:
https://github.com/apache/flink/pull/3703
where can i watch the status page-thing.. that tells us when we can get off
of old 2.11 ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user joan38 commented on the issue:
https://github.com/apache/flink/pull/3703
@StephanEwen Nice! That looks promising.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/3703
@joan38 I have some WIP for a flag that allows you to use vanilla akka when
running on Java 8, Scala 2.11
Here is the branch:
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/3703
There is about 10% Flink users on Java 7 (we did a poll recently).
Big clusters change slowly...
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user joan38 commented on the issue:
https://github.com/apache/flink/pull/3703
> Java 7 Reaches End of Life. Oracle ceased public availability of security
fixes and upgrades for Java 7 as of April 2015
We are in 2017
@StephanEwen but I understand if there is people
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/3703
@joan - I actually agree with you. We needed to use "flakka" to be able to
support Java 7 and bind to a wildcard address (across interfaces).
Would be great to be able to do that
Github user joan38 commented on the issue:
https://github.com/apache/flink/pull/3703
Going into the direction of dropping flakka would be a good win for users
of Flink like us that are dealing everyday with SBT/Maven hacking to be able to
use vanilla Akka and Flink.
---
If your
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/3703
We cannot add any other dependencies to the pom files. Adding "akka" back
will create a conflict with the "flakka" files.
What we can do is wither of the following two options:
-
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/3703
One thing you can try and do is to run
`TypeExtractionUtils.checkAndExtractLambda` to see if it is a generated
serializable Lambda.
In the case of a Lambda, you could switch to a different
Github user DieBauer commented on the issue:
https://github.com/apache/flink/pull/3703
Ok, started looking into the issue a bit more.
It seems like it has to do with the new lambda generation in scala 2.12 and
not with the asm library.
From the scala 2.12-M3 release
Github user DieBauer commented on the issue:
https://github.com/apache/flink/pull/3703
I'm running into an issue with asm in for example the flink-scala module,
when compiling with 2.12.
```
java.io.IOException: Class not found
at
Github user greghogan commented on the issue:
https://github.com/apache/flink/pull/3703
@DieBauer thanks for taking this on! I haven't been using Flink with Scala
but I think this will be important to have for the May release.
The required changes for type inferences are
21 matches
Mail list logo
