[jira] [Commented] (NIFI-12371) Support tombstone messages in non-record Kafka processors

["ASF subversion and git services (Jira)" <ji...@apache.org>]

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

ASF subversion and git services commented on NIFI-12371:
--------------------------------------------------------

Commit ee2368e0ae684d8a3ca2e62ce89422a2e260bdce in nifi's branch refs/heads/main from Pierre Villard
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=ee2368e0ae ]

NIFI-12371 Support tombstone messages in non-record Kafka processors

This closes #8076

Signed-off-by: David Handermann <ex...@apache.org>


> Support tombstone messages in non-record Kafka processors
> ---------------------------------------------------------
>
>                 Key: NIFI-12371
>                 URL: https://issues.apache.org/jira/browse/NIFI-12371
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Pierre Villard
>            Assignee: Pierre Villard
>            Priority: Minor
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> In some scenarios (compaction, transactions, etc), you may have Kafka tombstone messages (ie. the message has null for the content) and it may be important to have NiFi properly consume and publish those tombstone messages. As of now, when consuming Kafka messages, there is no way to differentiate a message that would be null (tombstone) and a message with an empty string). Also, as of now, when publishing a Kafka message, there is no way to send a null message, it would always be an empty string (empty byte array).
> This JIRA is about adding support for tombstone messages in ConsumeKafka_2_6 and PublishKafka_2_6 when not using a message demarcator. Follow up JIRAs could be filed to add support in the record based processors.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)