You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "blueberrysugarhigh (via GitHub)" <gi...@apache.org> on 2023/01/25 02:17:12 UTC

[GitHub] [kafka] blueberrysugarhigh commented on pull request #12126: KAFKA-8713 KIP-581: Add new conf serialize.accept.optional.null in connect-json

blueberrysugarhigh commented on PR #12126:
URL: https://github.com/apache/kafka/pull/12126#issuecomment-1402996186

   > @rayokota sorry for bothering you. I'm trying to maintain my own version of `JsonConverter`. I just copied the code and pasted it to a new class `JsonConverter`. and I replaced the following line
   > 
   > https://github.com/a0x8o/kafka/blob/283d07f9d2577e78b7aab7a419818cf9cda19d0a/connect/json/src/main/java/org/apache/kafka/connect/json/JsonConverter.java#L664
   > 
   > to
   > 
   > ```java
   > obj.set(field.name(), this.convertToJson(field.schema(), struct.getWithoutDefault(field.name())));
   > ```
   > 
   > Then I changed my debezium config to
   > 
   > ```
   >         ...
   >         "key.converter": "org.apache.kafka.connect.json.MyJsonConverter",
   >         "key.converter.schemas.enabled": true,
   >         "value.converter": "org.apache.kafka.connect.json.MyJsonConverter",
   >         "value.converter.schemas.enabled": true,
   > ```
   > 
   > but seems it still does not work. I still got default value with an nullable field. do u know why? what else do I need to do?
   
   Have you been able to make this work ? I just ran into the same issue. I upgraded my schema registry version and tried using the configuration in the connector, but it still was showing the wrong data. 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: jira-unsubscribe@kafka.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org