[
https://issues.apache.org/jira/browse/NIFI-11763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748456#comment-17748456
]
Dirk Hennig commented on NIFI-11763:
------------------------------------
Good morning David, understood, and this makes perfect sense if I reference s
static parameter name. But when I dynamically lookup multiple parameter based
on several flowfile attributes, then a restart would not have any effect or
benefit. For me a processor using evaluateELString would not be in scope for
restarting referencing components, because the name to lookup changes with any
flowfile anyway.
Yes, that is what I did, I frequently export all parameters to a DB and use
another processor to lookup my parameters based on current flowfile attribues.
This works fine, it is just more overhead to seek on external resources.
Thanks and greetings, Dirk
> 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)
