[
https://issues.apache.org/jira/browse/NIFI-5794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16680672#comment-16680672
]
ASF GitHub Bot commented on NIFI-5794:
--------------------------------------
Github user ijokarumawak commented on the issue:
https://github.com/apache/nifi/pull/3159
LGTM +1. I was able to confirm the expected benefit of using an empty
demarcator string to combine multiple Avro formatted Kafka messages into a
single FlowFile. Thanks @pvillard31!
For those who want to use this improvement with older NiFi versions, using
EL `${empty}` can mimic the non-empty validation and result the same effect .
This assumes there's no variable named `empty`, the EL evaluation result will
be an empty string while this is a valid configuration since it's not an empty
property value.
> ConsumeKafka and PublishKafka should allow empty string demarcator
> ------------------------------------------------------------------
>
> Key: NIFI-5794
> URL: https://issues.apache.org/jira/browse/NIFI-5794
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Pierre Villard
> Assignee: Pierre Villard
> Priority: Major
>
> ConsumeKafka processors should allow "empty string" as a message demarcator.
> This would allow consuming Avro data without the
> serialization/de-serialization cost while still allowing the use of Record
> processors once the data is in NiFi.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
