You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Michael W Moser (Jira)" <ji...@apache.org> on 2024/07/15 15:42:00 UTC

[jira] [Commented] (NIFI-13547) UpdateAttribute Advanced Configuration does not recognize Parameters

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

Michael W Moser commented on NIFI-13547:
----------------------------------------

Hi [~christof]  I see your example uses #replacement_parameter, but did you try #\{replacement_parameter}?  You still use Expression Language to access parameters.

> UpdateAttribute Advanced Configuration does not recognize Parameters
> --------------------------------------------------------------------
>
>                 Key: NIFI-13547
>                 URL: https://issues.apache.org/jira/browse/NIFI-13547
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 1.21.0, 1.23.2
>            Reporter: Christof Dilcher
>            Priority: Minor
>         Attachments: Parameter_Test.json.zip, direct_use_of_parameter_in_UpdateAttribute.jpg, parameter_used_in_expression_language_in_UpdateAttribute.jpg
>
>
> When using UpdateAttribute Advanced Configuration and configuring a rule, a parameter value (from the parameter context) is not directly accessible. When referencing a parameter in the "Value" section of the "Action" part of the "Rule" setup (see screenshot direct_use_of_parameter_in_UpdateAttribute.jpg), it is instead interpreted literally and not replaced with the parameter value as would be expected.
> The value can be accessed however when the parameter is referenced within an expression language term (see screenshot parameter_used_in_expression_language_in_UpdateAttribute.jpg).
> IMHO the parameter value shall be directly accessible within this configuration. If this is intended behavior, this shall be mentioned in the documentation as it is not obvious to the user that in this place the expression language has to be used in order to access the parameter value.
> I have attached the flow definition to this ticket (see Parameter_Test.json.zip) for reference. The corresponding parameter context just contains one parameter named "replacement_parameter" with its value 'some replacement value'.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)