[
https://issues.apache.org/jira/browse/NIFI-11763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748328#comment-17748328
]
David Handermann commented on NIFI-11763:
-----------------------------------------
Thanks for the reply and additional background.
Although the expression language evaluation could selective check for sensitive
status, the larger problem is that this approach to parameter references
impacts integration with Parameter Contexts. Changing a Parameter requires
restarting components, and the framework evaluates referencing components based
on static parameter name references. Constructing parameter name references in
an expression does not allow for the reference evaluation.
As you mentioned, it sounds like it is necessary to evaluate another way to
retrieve dynamic host information, such as through a Controller Service that
could have a database-backed implementation.
> evaluateELString not evaluating ContextParameters
> -------------------------------------------------
>
> Key: NIFI-11763
> URL: https://issues.apache.org/jira/browse/NIFI-11763
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.21.0, 1.22.0
> Environment: Linux NiFi 3 nodes cluster - 8 CPU core +32 GB of RAM
> per node
> Reporter: Dirk Hennig
> Priority: Major
> Attachments: Complex_UpdateAttribute_Test.json
>
>
> When using Expression Language it was possible to lookup parameters from
> ContextParameters and variables from VariableRegistry. Examples:
> ${ literal('#\{Tenant-Testing-HOST1}'):evaluateELString() }
> ${ literal('${Testvar}'):evaluateELString() }
> Both were working in NiFi 1.18.0. Now with NiFi version 1.21.0 this stopped
> working for ContextParameters and only lookups of varaibles are working.
> Please see the attached template with an example flow.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
