#187 Add details on interactions between Scala and Kryo #193
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As describe in the issue and this comment #187 (comment), here is a proposal to add more details of interactions between Scala and Kryo and explain the case where the duplication of case objects can occur.
First point of comment is addressed by adding some context:
Second point:
flink-scala
dependency was made.flink-scala
dependency is removed and Kryo is used.As a first step for the third point, recommend to disable Kryo to fail-fast, at least in a test environment.