[
https://issues.apache.org/jira/browse/NIFI-14566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard updated NIFI-14566:
----------------------------------
Status: Patch Available (was: Open)
> Introduce Inject Metadata Output Strategy in ConsumeKafka
> ---------------------------------------------------------
>
> Key: NIFI-14566
> URL: https://issues.apache.org/jira/browse/NIFI-14566
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Pierre Villard
> Assignee: Pierre Villard
> Priority: Major
>
> The Output Strategy in Consume Kafka (when using Record) currently supports
> two options
> * USE_VALUE
> * USE_WRAPPER
> With USE_VALUE, the record read from the Kafka message will be the output of
> the record in the flow file.
> With USE_WRAPPER, the record read from the Kafka message will be used as a
> sub-record of a new record with specific fields (value for the record read
> from the kafka message, metadata for some metadata from the kafka message,
> headers and key).
> The goal is to introduce another strategy INJECT_METADATA, where we keep the
> record read from the kafka message and update its schema to add one sub
> record field to include all of the metadata (metadata, headers and key).
> This can be interesting when the user provides a schema to read the data from
> Kafka and wants to retain that schema while still having the option to have
> the metadata if needed. In case the user leverages record oriented
> processors, the user does not need to use prefixed record paths (like
> /value/myField) but can directly use record paths that are matching their
> schema (/myField).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
