[
https://issues.apache.org/jira/browse/NIFI-8173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Witt updated NIFI-8173:
---------------------------
Fix Version/s: 1.13.0
> Parameter values should consistently allow for Expression Language
> ------------------------------------------------------------------
>
> Key: NIFI-8173
> URL: https://issues.apache.org/jira/browse/NIFI-8173
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework, Documentation & Website
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.13.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The User Guide claims that Parameters cannot make use of Expression Language.
> And if a processor/controller service uses
> {code:java}
> context.getProperty(DESCRIPTOR).evaluateAttributeExpresssions().getValue();
> {code}
> It does, in fact, not evaluate EL.
> However, UpdateAttribute uses a different API
> (ProcessContext.newPropertyValue(...) ) and in the API it DOES evaluate EL.
> We need to be consistent in how we are evaluating (or not) the Expression
> Language.
> We do see use cases where allowing Expression Language within Parameters will
> be very useful, so I would lean toward allowing EL to be used. This will
> require that the User Guide also be updated to clearly explain the context in
> which the EL will be evaluated.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
