[
https://issues.apache.org/jira/browse/NIFI-6077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rabits updated NIFI-6077:
-------------------------
Description:
For some reason right now extensions decide where to use and where don't NFEL -
that's bummer. It makes complete automation impossible and DevOps unhappy.
I think it will be good to twist this not a good practice and give users more
freedom in using Expression Language / Variables whenever they want! And I
think it could be solved by introducing forceEl flag for PropertyDescriptor,
that could be set by user and saved with property value.
With the change we can deprecate the old complex and non-intuitive setting
support of EL in the extensions and even set forceEl by default for some
extensions that already supporting EL scopes.
I'm already working on the first implementation here:
https://github.com/apache/nifi/pull/3332
was:
For some reason right now extensions decide where to use and where don't NFEL -
that's bummer. It makes complete automation impossible and DevOps unhappy.
I think it will be good to twist this not a good practice and give users more
freedom in using Expression Language / Variables whenever they want! And I
think it could be solved by introducing forceEl flag for PropertyDescriptor,
that could be set by user and saved with property value.
With the change we can deprecate the old complex and non-intuitive setting
support of EL in the extensions and even set forceEl by default for some
extensions that already supporting EL scopes.
I'm already working on the first implementation here:
[https://github.com/rabits/nifi/tree/force_el]
> Expression Language Force - give users decide where to use EL
> -------------------------------------------------------------
>
> Key: NIFI-6077
> URL: https://issues.apache.org/jira/browse/NIFI-6077
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Configuration, Core Framework, Core UI, Variable Registry
> Affects Versions: 1.9.0
> Reporter: Rabits
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> For some reason right now extensions decide where to use and where don't NFEL
> - that's bummer. It makes complete automation impossible and DevOps unhappy.
> I think it will be good to twist this not a good practice and give users more
> freedom in using Expression Language / Variables whenever they want! And I
> think it could be solved by introducing forceEl flag for PropertyDescriptor,
> that could be set by user and saved with property value.
> With the change we can deprecate the old complex and non-intuitive setting
> support of EL in the extensions and even set forceEl by default for some
> extensions that already supporting EL scopes.
>
> I'm already working on the first implementation here:
> https://github.com/apache/nifi/pull/3332
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
