Skip to content

GH-1401 Use content-type for Kafka CloudEvents#1420

Closed
goutamadwant wants to merge 1 commit into
spring-cloud:mainfrom
goutamadwant:GH-1401
Closed

GH-1401 Use content-type for Kafka CloudEvents#1420
goutamadwant wants to merge 1 commit into
spring-cloud:mainfrom
goutamadwant:GH-1401

Conversation

@goutamadwant

Copy link
Copy Markdown
Contributor

Summary

  • Map CloudEvents datacontenttype to the Kafka binary-mode content-type header when building messages with the Kafka attribute prefix
  • Keep default-prefix CloudEvents using ce-datacontenttype
  • Allow CloudEventMessageUtils.getDataContentType to read the Kafka binary-mode content-type header

Closes: gh-1401

Testing

  • ./mvnw -pl spring-cloud-function-context -Dtest=CloudEventMessageUtilsAndBuilderTests test
  • ./mvnw -pl spring-cloud-function-context test

Signed-off-by: Goutam Adwant <workwithgoutam@gmail.com>
@olegz olegz closed this in 0d7ef99 Jul 9, 2026
olegz added a commit that referenced this pull request Jul 9, 2026
Resolves #1420
Resolves #1401

Signed-off-by: Oleg Zhurakousky <ozhurakousky@vmware.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CloudEventMessageBuilder.setDataContentType() writes ce_datacontenttype header instead of content-type in Kafka binary mode

1 participant