ZhiQiang-Tiger commented on issue #2093: URL: https://github.com/apache/fury/issues/2093#issuecomment-2706707345
The issue arises because Fury assigns values to class fields by sorting them based on their fully qualified class names. During serialization, the order of classes was A -> B -> D. However, after modifying the classpath during deserialization, the order became D -> A -> B. Although the registration order of classes during deserialization can be adjusted to A -> B -> D, the actual assignment process still follows the fixed order dictated by the sorted fully qualified class names. When Fury attempts to parse and assign the first deserialized object (originally class A) to the first position in the sorted order (now class D), it results in a ClassCastException because class A cannot be cast to class D. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
