Github user asfgit closed the pull request at:
https://github.com/apache/flink/pull/1528
---
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 enab
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" wrote:
> Trigger was a mail from Theo on the ML where deserialization failes in the
> r
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/1528#issuecomment-173314485
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
Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/1528#issuecomment-173276572
Just curious, was there an issue with this? Or how did you stumble upon the
reference tracking?
---
If your project is set up for it, you can reply to this email a
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 JavaSeri
