Avro serialization failing because of unknown property #3436
Assignees
Comments
fjtirado
added a commit
to fjtirado/kogito-runtimes
that referenced
this issue
Mar 11, 2024
fjtirado
added a commit
to fjtirado/kogito-runtimes
that referenced
this issue
Mar 12, 2024
fjtirado
added a commit
to fjtirado/kogito-runtimes
that referenced
this issue
Mar 12, 2024
fjtirado
added a commit
to fjtirado/kogito-runtimes
that referenced
this issue
Mar 12, 2024
fjtirado
added a commit
to fjtirado/kogito-runtimes
that referenced
this issue
Mar 12, 2024
fjtirado
added a commit
to fjtirado/kogito-runtimes
that referenced
this issue
Mar 12, 2024
github-project-automation
bot
moved this from 📋 Backlog
to 🎯 Done
in 🦉 KIE Podling Board
rgdoliveira
pushed a commit
to rgdoliveira/kogito-runtimes
that referenced
this issue
Mar 27, 2024
* [Fix apache#3436] Ignoring unknown properties * [Fix apache#3436] Adding unit test
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
It turns out that current serializes is sensible to additional getters on generated Avro class
Expected behavior
Pojo is serialized into binary stream
Actual behavior
Jackson serialization exception
How to Reproduce?
See https://kie.zulipchat.com/#narrow/stream/232676-kogito/topic/trouble.20using.20AvroCloudEventMarshaller/near/425936424
Output of
uname -aorverNo response
Output of
java -versionNo response
GraalVM version (if different from Java)
No response
Kogito version or git rev (or at least Quarkus version if you are using Kogito via Quarkus platform BOM)
No response
Build tool (ie. output of
mvnw --versionorgradlew --version)No response
Additional information
The text was updated successfully, but these errors were encountered: