Skip to content

fix: use incoming object if schema is not defined#184

Merged
ali-ince merged 3 commits intoneo4j:mainfrom
ali-ince:support-kafka-json-converter
Sep 24, 2024
Merged

fix: use incoming object if schema is not defined#184
ali-ince merged 3 commits intoneo4j:mainfrom
ali-ince:support-kafka-json-converter

Conversation

@ali-ince
Copy link
Contributor

This PR fixes an issue where org.apache.kafka.connect.json.JsonConverter is not supported when schemas.enable is set to false which should support incoming JSON strings.

@ali-ince ali-ince requested a review from a team as a code owner September 23, 2024 13:15
@ali-ince ali-ince changed the title fix: use incoming object is schema is not defined fix: use incoming object if schema is not defined Sep 23, 2024
@ali-ince ali-ince enabled auto-merge (squash) September 24, 2024 08:19
@ali-ince ali-ince merged commit 246bb6d into neo4j:main Sep 24, 2024
@TomVanWemmel
Copy link

Hello,
Thank you for fixing this issue! It is currently blocking us from migrating the 5.0 connectors to 5.1.
Is the release for this fix planned soon?

@Emrehzl94
Copy link
Contributor

Hello, Thank you for fixing this issue! It is currently blocking us from migrating the 5.0 connectors to 5.1. Is the release for this fix planned soon?

Hello, please check the release here; https://github.com/neo4j/neo4j-kafka-connector/releases/tag/5.1.2

@neo4j neo4j deleted a comment from Emrehzl94 Oct 4, 2024
@ali-ince ali-ince deleted the support-kafka-json-converter branch November 22, 2024 15:59
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.

4 participants