GitHub user chaokunyang added a comment to the discussion: (Java/Scala) How do I specify deserialize behavior on schema change?
However, I think it's possible to providea callback to let users handle such situations. It's possible to extend Fury to pass objects and incompatible fields to users to let them handle such cases GitHub link: https://github.com/apache/fury/discussions/1848#discussioncomment-10714510 ---- This is an automatically sent email for commits@fury.apache.org. To unsubscribe, please send an email to: commits-unsubscr...@fury.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@fury.apache.org For additional commands, e-mail: commits-h...@fury.apache.org