[
https://issues.apache.org/jira/browse/NIFI-15859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-15859:
------------------------------------
Fix Version/s: 2.10.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Correct ExecuteGroovyScript Documentation to Indicate Dynamic Property
> Expression Language Scope is ENVIRONMENT
> ---------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-15859
> URL: https://issues.apache.org/jira/browse/NIFI-15859
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Daniel Stieglitz
> Assignee: Daniel Stieglitz
> Priority: Minor
> Fix For: 2.10.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> There is a conflict between the documentation of ExecuteGroovyScript and the
> actual implementation regarding the Expression Language Scope of dynamic
> properties. The documentation on lines 80-85 indicates dynamic properties
> have Expression Language Scope FLOWFILE_ATTRIBUTES while the code on lines
> 580-587:
> indicates the Expression Language Scope is ENVIRONMENT.
> It seems this may have been introduced back in PR
> [#2205|https://github.com/apache/nifi/pull/2205] when the scope was
> {{VARIABLE_REGISTRY}} and the annotation was added indicating the Expression
> Language Scope is {{FLOWFILE_ATTRIBUTES}} . Then in PR
> [#7750|https://github.com/apache/nifi/pull/7750] the Expression Language
> Scope was changed from {{VARIABLE_REGISTRY}} to {{ENVIRONMENT}} . So it seems
> the correct scope should be {{ENVIRONMENT}} .
> The goal of this ticket is align the documentation with the code and indicate
> the Expression Language Scope is ENVIRONMENT.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
