[
https://issues.apache.org/jira/browse/NIFI-11763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17742803#comment-17742803
]
David Handermann commented on NIFI-11763:
-----------------------------------------
Thanks for the reply Dirk.
If I understand correctly, it sounds like your flow has a Parameter Context
that defines several SFTP host names, and you want to reuse the same PutSFTP
Processor in the flow, instead of configuring multiple instances and routing to
each one? I can see how that could, effectively trading flow design
configuration for parameter lookup.
Although it is more complicated than the previous approach with
evaluateELString() to lookup a Parameter, it should be possible to use
UpdateAttribute with the Advanced configuration to list all possible SFTP host
names, and then use the advanced conditionals to select the appropriate values.
That should allow using the same PutSFTP Processor with the selected attribute
value coming out of UpdateAttribute.
> 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)
