GitHub user StephanEwen opened a pull request:

    https://github.com/apache/flink/pull/1528

    [FLINK-3267] Disable reference tracking in Kryo fallback serializer

    Before this commit, Kryo runs extra logic to track and resolve repeated 
references to
    the same object (similar as JavaSerialization)
    
    This disables reference tracking because
      - reference tracking is costly
      - it is virtually always unnecessary in the datatypes used in Flink
      - 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.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/StephanEwen/incubator-flink kryo

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/1528.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1528
    
----
commit cb94002f4b38090d21e0baadbd5964ebb9c4de9d
Author: Stephan Ewen <[email protected]>
Date:   2016-01-20T15:26:58Z

    [FLINK-3267] Disable reference tracking in Kryo fallback serializer
    
    Before this commit, Kryo runs extra logic to track and resolve repeated 
references to
    the same object (similar as JavaSerialization)
    
    This disables reference tracking because
      - reference tracking is costly
      - it is virtually always unnecessary in the datatypes used in Flink
      - 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.

----


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to