[
https://issues.apache.org/jira/browse/NIFI-8661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Burgess updated NIFI-8661:
-------------------------------
Fix Version/s: 1.14.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Update Record Reader/Writer lookup services to not require specific
> attributes exist
> ------------------------------------------------------------------------------------
>
> Key: NIFI-8661
> URL: https://issues.apache.org/jira/browse/NIFI-8661
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.14.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> NIFI-5829 introduced a ReaderLookup service and a RecordSetWriterLookup
> service. However, these services make the assumption that the reader/writer
> to use exists on an attribute of the flowfile such as {{recordreader.name}}.
> This means that these services are not applicable for many situations,
> especially for source processors.
> A more convenient way would be to just add a property to these services
> indicating the name of the service to use, instead of expecting that an
> attribute with that name exists. We can set the default value of the property
> to `${recordreader.name}` etc. in order to maintain backward compatibility.
> But this gives us the flexibility, for example, to use this in
> ConsumeKafkaRecord where kafka message headers are available in Expression
> Language and also gives us the ability to use a parameter for specifying the
> data format to use.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
