You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Gunnar Morling (JIRA)" <ji...@apache.org> on 2018/12/12 16:16:00 UTC

[jira] [Commented] (KAFKA-3832) Kafka Connect's JSON Converter never outputs a null value

    [ https://issues.apache.org/jira/browse/KAFKA-3832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16719137#comment-16719137 ] 

Gunnar Morling commented on KAFKA-3832:
---------------------------------------

What would be the right fix to this issue then, could it simply be changed to return a null value in this case? That should be simple enough, but I'm wondering whether there'll be a problem if some records have a schema (non-tombstones) and some others don't (tombstones).

> Kafka Connect's JSON Converter never outputs a null value
> ---------------------------------------------------------
>
>                 Key: KAFKA-3832
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3832
>             Project: Kafka
>          Issue Type: Bug
>          Components: KafkaConnect
>    Affects Versions: 0.9.0.1
>            Reporter: Randall Hauch
>            Assignee: Prasanna Subburaj
>            Priority: Major
>              Labels: newbie
>
> Kafka Connect's JSON Converter will never output a null value when {{enableSchemas=true}}. This means that when a connector outputs a {{SourceRecord}} with a null value, the JSON Converter will always produce a message value with:
> {code:javascript}
> {
>   "schema": null,
>   "payload": null
> }
> {code}
> And, this means that while Kafka log compaction will always be able to remove earlier messages with the same key, log compaction will never remove _all_ of the messages with the same key. 
> The JSON Connector's {{fromConnectData(...)}} should always return null when it is supplied a null value.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)