Hi Dmitry,
do you maybe have a more complete stack trace? I have a suspicion but I
would like to confirm that.
Best,
Aljoscha
On Fri, 17 Feb 2017 at 20:24 Dmitry Golubets wrote:
> Hi Till,
>
> It happened during deserialization of a savepoint.
>
> Best regards,
> Dmitry
>
> On Fri, Feb 17, 2017
Hi Till,
It happened during deserialization of a savepoint.
Best regards,
Dmitry
On Fri, Feb 17, 2017 at 2:48 PM, Till Rohrmann wrote:
> Hi Dmitry,
>
> curious to know when exactly you observed the IllegalStateException. Did
> it happen after resuming from a savepoint or did it already happen
Hi Dmitry,
curious to know when exactly you observed the IllegalStateException. Did it
happen after resuming from a savepoint or did it already happen during the
first run of the program? If the latter is the case, then this might
indicate a bug where we don’t use the correct ExecutionConfig to
in
Hi,
I was using ```cs.knownDirectSubclasses``` recursively to find and register
subclasses, which may have resulted in order mess.
Later I changed that to
cs.knownDirectSubclasses.toList.sortBy(_.fullName)``` which should have
fixed the order.
But either it didn't or there was another problem,
Hi,
are you changing anything on your job between performing the savepoint and
restoring the savepoint? Flink upgrade, Job upgrade, changing Kryo version,
changing order in which you register Kryo serialisers?
Best,
Aljoscha
On Fri, 10 Feb 2017 at 18:26 Dmitry Golubets wrote:
> The docs say tha
The docs say that it may improve performance.
How true is it, when custom serializers are provided?
There is also 'disableAutoTypeRegistration' method in the config class,
implying Flink registers types automatically.
So, given that I have an hierarchy:
trait A
class B extends A
class C extends A
