-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Add apicurio protobuf support #37981
Add apicurio protobuf support #37981
Conversation
aa5291d
to
a3af5f8
Compare
The problem with the native integration test is that when the test is executed in that mode, the runtime used for generating the class and the one used for running the test is different, causing protobuf to fail validating the message. The flow and test works fine in JVM mode, and that might be all that can be done here. |
a3af5f8
to
43ebc1d
Compare
This comment has been minimized.
This comment has been minimized.
a632761
to
5c24e10
Compare
@alesj can you have a look? |
@cescoffier yeah, already on my todo list for this week -- all coordinated with @carlesarnal |
5c24e10
to
267407b
Compare
@alesj now the error must be reproducible. Note that I had to revert the banned dependency, so I'm going to close the PR for now so it does not get merged by mistake. |
This introduces support for serialization using protobuf as #37722 introduced for JSON Schema. The caveat here is that Protobuf serialization does not work for now in native mode. I will investigate more.