You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Prasanna Subburaj (JIRA)" <ji...@apache.org> on 2018/01/27 00:56:03 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=16341864#comment-16341864 ]
Prasanna Subburaj commented on KAFKA-3832:
------------------------------------------
[~rhauch]: So should we at least let the user that we they should not use enableSchemas=true ?
Should we handle the messages when enableSchema=true and they are sending messages throw exception ? Please advice ?
> 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
> 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)