Github user rmetzger commented on the issue:
    This change adds Kryo-shaded to our dependency tree:
    [INFO] |  +- com.twitter:chill_2.10:jar:0.8.1:compile
    [INFO] |  |  +- com.twitter:chill-java:jar:0.8.1:compile
    [INFO] |  |  \- com.esotericsoftware:kryo-shaded:jar:3.0.3:compile
    [INFO] |  |     \- com.esotericsoftware:minlog:jar:1.3.0:compile
    I suspect that maven is not recognizing this because chill seems to depend 
on `kryo-shaded`.
    Apparently, `kryo-shaded` has a shaded ASM version included, but it is not 
relocating the regular Kryo classes. So we'll end up having two Kryo versions 
in our classpath.
    So if we want to upgrade Kryo, we need to do it explicitly, to avoid having 
two Kryo versions in our classpath.
    Another issue we need to consider is the serialization compatibility. 
Savepoints in Flink could potentially contain data serialized with Kryo 2.24. 
If we want to provide savepoint compatibility between Flink 1.1 and 1.2, we 
need to consider that.
    According to the Kryo documentation, 2.24 to 3.0.0 is serialization 
compatible (I hope the same holds true for chill):
    I would like to hear @StephanEwen and @uce's opinion on 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
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

Reply via email to