You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/03/19 14:28:00 UTC

[jira] [Commented] (NIFI-8328) Pass FlowFile attributes to RestLookupService

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

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

Commit 446401b6f153df9260349050ae228fda5ca98525 in nifi's branch refs/heads/main from Matt Burgess
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=446401b ]

NIFI-8328: Allow RestLookupService to use FlowFile attributes in header properties

This closes #4908

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


> Pass FlowFile attributes to RestLookupService
> ---------------------------------------------
>
>                 Key: NIFI-8328
>                 URL: https://issues.apache.org/jira/browse/NIFI-8328
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Matt Burgess
>            Assignee: Matt Burgess
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently RestLookupService's user-defined properties are used to define header values for the REST call, but they are determined when the controller service is enabled, and thus cannot use FlowFile attributes. This could be done when the lookup is performed, thereby allowing FlowFile attributes in the header property expressions.
> Also the documentation is incorrect, it does not provide an Expression Language Scope so defaults to "None", but evaluateAttributeExpressions() is called on the user-defined properties. The documentation should match the behavior.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)