[
https://issues.apache.org/jira/browse/NIFI-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395026#comment-15395026
]
ASF GitHub Bot commented on NIFI-2208:
--------------------------------------
Github user YolandaMDavis commented on the issue:
https://github.com/apache/nifi/pull/571
@JPercivall thanks for the review! Just wanted to add a couple of notes on
questions you had above:
> @YolandaMDavis, what happens if an incoming FlowFile,
FileVariableRegistry and custom EL attributes all have the same key? Is there
any ordering enforced? From looking at the code, I believe it to be random.
>
The order is dictated through the MultiMap's (now ImmutableMultiMap) use of
an ArrayList internally which maintains the order in which a map was added to
that list. In the case you mentioned where the same key name appears across a
flow file, file/property registry etc the first map encountered in the
ImmutableMultiMap's list with that value will be used.
When the variable registry is initialized via VariableRegistryUtils (as it
is in most of the application) environment variables and java application
properties are added first, with those values taking precedence.
The details of this will be added to the admin guide (which I believe is
part of another issue on Jira list, but I can confirm).
> Support Custom Properties in Expression Language - 1.x baseline
> ---------------------------------------------------------------
>
> Key: NIFI-2208
> URL: https://issues.apache.org/jira/browse/NIFI-2208
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Yolanda M. Davis
> Priority: Blocker
> Fix For: 1.0.0
>
>
> NIFI-1974 addressed this for the 0.x baseline but the PR does not apply
> cleanly to the 1.x baseline. Creating a separate JIRA for 1.x so that we can
> close out NIFI-1974 since 0.7.0 is ready to be released.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
