Closed marcospassos closed 3 years ago
Sigh. No idea what specifically would be, although guessing that from databind fixes, either issue 2821 or 2846 might be relevant. Low level exception itself suggests loss of type information somewhere, type resolution failing.
I doubt this is Avro-specific, wondering if this:
https://github.com/FasterXML/jackson-databind/issues/2876
might be due to same root cause, whatever it is.
Actually, more like this one:
https://github.com/FasterXML/jackson-databind/issues/2876
which is fixed and will be included in 2.11.4 (not yet out).
Just for clarity, is this a hypothesis, or have you checked if this issue goes away with this fix?
@marcospassos Without reproduction of the problem it is just a hypothesis, but symptoms and fix in question seem quite plausible. So if you have an easy way to verify it would be good to find out either way -- I hope to release 2.11.4 soon, before going on for my christmas break.
Fwtw, 2.11.4 was released 12-Dec-2020. Then again 2.12 is out, latest being 2.12.3 as well.
At this point, a unit test would be required to reproduce the problem if it still remains.
We updated our codebase to 2.11.3 and started getting the following error everywhere:
For some reason, some classes cannot get deserialized (we're using mixins with builders).
Any idea what was introduced in 2.11.3 that can be causing these errors?