[ https://issues.apache.org/jira/browse/FLINK-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15110317#comment-15110317 ]
ASF GitHub Bot commented on FLINK-3267: --------------------------------------- Github user tillrohrmann commented on the pull request: https://github.com/apache/flink/pull/1528#issuecomment-173509879 Sure makes sense :-) On Jan 20, 2016 7:23 PM, "Stephan Ewen" <notificati...@github.com> wrote: > Trigger was a mail from Theo on the ML where deserialization failes in the > reference mapper. There may be another issue still, but a failure in a code > that is better not executed seemed avoidable ;-) > > — > Reply to this email directly or view it on GitHub > <https://github.com/apache/flink/pull/1528#issuecomment-173314485>. > > Disable reference tracking in Kryo fallback serializer > ------------------------------------------------------ > > Key: FLINK-3267 > URL: https://issues.apache.org/jira/browse/FLINK-3267 > Project: Flink > Issue Type: Bug > Components: Local Runtime > Affects Versions: 0.10.1 > Reporter: Stephan Ewen > Assignee: Stephan Ewen > Priority: Blocker > Fix For: 1.0.0 > > > Kryo runs extra logic to track and resolve repeated references to the same > object (similar as JavaSerialization) > We should disable reference tracking > - reference tracking is costly > - it is virtually always unnecessary in the datatypes used in Flink > - most importantly, it is inconsistent with Flink's own serialization > (which does not do reference tracking) > - It may have problems if elements are read in a different order than they > are written. -- This message was sent by Atlassian JIRA (v6.3.4#6332)