[
https://issues.apache.org/jira/browse/NIFI-5367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard resolved NIFI-5367.
----------------------------------
Fix Version/s: (was: 2.0.0)
Resolution: Won't Do
Removal of variables for NiFi 2.0
> Enable EL support with Variable Registry scope by default
> ---------------------------------------------------------
>
> Key: NIFI-5367
> URL: https://issues.apache.org/jira/browse/NIFI-5367
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Pierre Villard
> Priority: Major
>
> With the Variable Registry feature in NiFi and the FDLC concepts with the
> NiFi Registry, there is a lot of traction to enable Expression Language with
> Variable Registry scope by default.
> I suggest we change the current behavior so that Variable Registry scope is
> set as the default scope even though {{.expressionLanguageSupported()}} is
> not specified when creating the property. However it should still be possible
> for a developer to disable Expression Language evaluation by setting the EL
> scope to None (it can make sense for properties expecting a regular
> expression for instance)
> This is going to be a breaking change for existing flows and that's why I'm
> tagging this JIRA for 2.0.0 for the time being. I believe this change should
> also be considered in a more global effort regarding how we can manage the
> sensitive properties with the Variable Registry (see discussion in NIFI-5296).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
