-
Notifications
You must be signed in to change notification settings - Fork 213
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
[Fix_3383] Adding binary cloud event support for outgoing messages #3386
Conversation
...odegen-core/src/main/resources/class-templates/config/GlobalObjectMapperQuarkusTemplate.java
Outdated
Show resolved
Hide resolved
This reverts commit 47b9b4d.
ba86a44
to
aa82aad
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, coverage comment mentioned on kogito-examples review.
Great work @fjtirado !
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code looks fine, I'm just wondering about what Matej said that CE SDK can handle the serialization for specific connectors, like HTTP and Kafka.
@ricardozanini In kogito, it was decided at the beginning to handle the serialization through custom marshallers rather than relying on connector specifics. However, if user want do to that, one of the provided marshallers is a not marshaller at all, which relies on the connector setup |
…pache#3386) * [Fix_3383] Do not include null values on json payload * Revert "[Fix_3383] Do not include null values on json payload" This reverts commit 47b9b4d. * [Fix_#3383] Setting metadata when using binary
…pache#3386) * [Fix_3383] Do not include null values on json payload * Revert "[Fix_3383] Do not include null values on json payload" This reverts commit 47b9b4d. * [Fix_#3383] Setting metadata when using binary
Knative has issues with structure event, so we are switching to binary, by defaullt, for quarkus-http connector.
This behaviour can be modified through configuration.
Users can specifiy
kogito.addon.messaging.outgoing.cloudEventMode.<channelName>=BINARY|STRUCTURED
to configure cloud event mode per outgoing channel
or just
kogito.addon.messaging.outgoing.cloudEventMode=BINARY|STRUCTURED
to set it overrall.
If nothing specified, binary is used for quarkus-http connector and structured for the others, to keep backward compatibility with existing examples using Kafka.
This requires changes on kogito-apps tests apache/incubator-kie-kogito-apps#1974 and examples apache/incubator-kie-kogito-examples#1862
Fixes #3383