-
Notifications
You must be signed in to change notification settings - Fork 827
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kryo does not correctly support parameterized type hierarchy #377
Comments
FYI @rkavanap |
Hi,
As you can see the error comes from the generic usage. If I remove the first serialization it fails. Best regards. |
I believe this is a regression from the following commit: 4764dee Reverting this commit causes this test to pass. The superclass for LongListHolder is AbstractValueListHolder, which is parameterized with Long. This is the type that is found in FieldSerializerGenericsUtil#buildGenericsScope at line 79. I'm not sure what the fix for this is, but at this point generic scope is set to Long, and Kryo ultimately gets a LongSerializer when it needs to serialize a list. |
Resolved by #433 |
Test case:
Error:
Cause:
Kryo reuses the same
CachedField
instance it previously encountered, but the type changed.The text was updated successfully, but these errors were encountered: