[ https://issues.apache.org/jira/browse/NIFI-5061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17199065#comment-17199065 ]
ASF subversion and git services commented on NIFI-5061: ------------------------------------------------------- Commit 953abba6d609f93f5b4e12772e25802007719901 in nifi's branch refs/heads/main from abrown [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=953abba ] NIFI-5061-NiFi documentation incomplete/wrong for EL hierarchy. Co-authored-by: Pierre Villard <pierre.villard...@gmail.com> Signed-off-by: Pierre Villard <pierre.villard...@gmail.com> This closes #4530. > NiFi documentation incomplete/wrong for EL hierarchy. > ----------------------------------------------------- > > Key: NIFI-5061 > URL: https://issues.apache.org/jira/browse/NIFI-5061 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website > Affects Versions: 1.5.0 > Environment: N/A > Reporter: Matthew Clarke > Assignee: Alasdair Brown > Priority: Major > Labels: newbie > Time Spent: 20m > Remaining Estimate: 0h > > Within the NiFi Expression Language Guide under the "Structure of a NiFi > Expression" section, the hierarchy of how NiFi searches for a Attribute key > is wrong (still based off NiFi 0.x hierarchy) and incomplete: > Current text: > In this example, the value to be returned is the value of the "my attribute" > value, if it exists. If that attribute does not exist, the Expression > Language will then look for a System Environment Variable named "my > attribute." If unable to find this, it will look for a JVM System Property > named "my attribute." Finally, if none of these exists, the Expression > Language will return a null value. > The current hierarchy in NiFi is as follows: > 1. Search FlowFile for Attribute/key > 2. Search Process Group for attribute/key > 3. Search File Registry File for attribute/key > 4. Search NiFi JVM Properties for attribute/key > 5. Search System Environment Variables for attribute/key > We should not only fix the above, but in doing so make the above hierarchy > more prominent in the documentation. -- This message was sent by Atlassian Jira (v8.3.4#803005)