[
https://issues.apache.org/jira/browse/NIFI-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Thomsen resolved NIFI-1380.
--------------------------------
Resolution: Duplicate
I think this ticket was already done by the work that added the
ExpressionLanguageScope functionality.
> Provide Expression Language scoping for properties
> --------------------------------------------------
>
> Key: NIFI-1380
> URL: https://issues.apache.org/jira/browse/NIFI-1380
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Aldrin Piri
> Priority: Minor
>
> Expression Language when applied to a property via a PropertyDescriptor can
> have different contexts in how it is applied. In one case, this can make use
> of just System Environment variables or JVM properties. However, if applied
> using the evaluateAttributeExpressions(FlowFile) method, this is done on a
> per FlowFile basis.
> Ideally we could provide some way for extension developers to communicate the
> intent of how these properties will be used.
> Perhaps adjusting PropertyDescriptor's builder method
> #expressionLanguageSupported(boolean) to
> #expressionLanguageSupported(boolean, ELScope) or similar would provide
> sufficient control. The auto generated documentation could use this to
> provide the associated indication of EL level.
> We could additionally have the test framework make use of this Scope to
> ensure that if something is/is not scoped to use FlowFile level EL that these
> are caught in testing.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
