I filed an issue for this: https://issues.apache.org/jira/browse/FLINK-8451
Am 1/12/18 um 4:40 PM schrieb Seth Wiesman:
Here is the stack trace:
org.apache.flink.streaming.runtime.tasks.StreamTaskException: Cannot
instantiate user function.
at
org.apache.flink.streaming.api.graph.Stre
Here is the stack trace:
org.apache.flink.streaming.runtime.tasks.StreamTaskException: Cannot
instantiate user function.
at
org.apache.flink.streaming.api.graph.StreamConfig.getStreamOperator(StreamConfig.java:235)
at
org.apache.flink.streaming.runtime.tasks.OperatorChain.(Oper
Hi Seth,
Thanks a lot for the report!
I think your observation is expected behaviour, if there really is a binary
incompatible change between Scala minor releases.
And yes, the type information macro in the Scala API is very sensitive to
the exact Scala version used. I had in the past also observ
This is less of a question and more of a PSA.
It looks like there is some sort of binary incompatible change in the scala
standard library class `scala.collection.immutable.::` between point releases
of scala 2.11. CaseClassTypeInfo generated by the type information macro will
fail to deserial
