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

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

Commit d340ad79ed82f3fa07ed37412ae686453029bf6f in nifi's branch 
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=d340ad7 ]

NIFI-8661: Updated ReaderLookup and RecordSetWriterLookup to use a property 
that indicates which reader/writer to use instead of requiring a specific 
attribute be provided

Signed-off-by: Matthew Burgess <[email protected]>

This closes #5129


> 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: 0.5h
>  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)

Reply via email to