Github user StephanEwen commented on the issue:
As far as I read it, Kryo 3.x is not strictly serialization compatible with
2.x, hence the major version number bump.
If the interfaces are still stable, then it should be fine to bump the
chill dependency version, exclude any kryo dependency, and add our own 2.x kryo
dependency. I would prefer that approach.
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 infrastruct...@apache.org or file a JIRA ticket