-
-
Notifications
You must be signed in to change notification settings - Fork 143
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
CachingParanamer breaks java.io.Serializable #266
Comments
Probably won't make much difference, but the latest is 2.7.4, so might make sense to try it just to make sure. As to problem itself, this would be Generally however it is often better to try to avoid getting Jackson's object mapper, reader or writer from getting in transitive closure that is serialized. If at all possible. It's still quite a bit of stuff to transfer, without much value (as long as it can be re-created by workers). |
Thanks, I caught this at the end of the day, too brain-dead to realize it's an easy workaround in scala using @transient lazy val. So there's no urgency at least for me. |
For what that is worth, it is fixed for paranamer module for next releases, (2.7.6 / 2.8.0) since mapper/reader/writer ought to remain serializable. |
using v 2.7.2, trying to serialize an ObjectReader instance (used in a Flink serialized function), I get this error:
com.fasterxml.jackson.module.paranamer.shaded.CachingParanamer
java.io.NotSerializableException: com.fasterxml.jackson.module.paranamer.shaded.CachingParanamer
I have verified that the ObjectReader instance does serialize correctly id the DefaultScalaModule is not registered. Is there a workaround for this?
The text was updated successfully, but these errors were encountered: