[
https://issues.apache.org/jira/browse/NIFI-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15322323#comment-15322323
]
ASF GitHub Bot commented on NIFI-1974:
--------------------------------------
Github user YolandaMDavis commented on the issue:
https://github.com/apache/nifi/pull/501
@markap14 Thanks for reviewing! Concerning the extension of
VariableRegistryProvider by the ControllerServiceLookup, it came from the need
to populate the VariableRegistry from NiFiProperties, if available, (which was
provided by implementations of ControllerServiceLookup, including
FlowController, WebClusterManager) and provide it to StatePropertyValue (which
received a ControllerServiceLookup object in it's constructor). I thought about
having a third variable in the constructor for StatePropertyValue for the
variableRegistry however when attempting to implement I needed to interrogate
the ControllerServiceLookup anyway in many cases. I definitely understand the
weirdness which is why a the least I had it extend the interface as opposed to
adding the getVariableRegistry method to that interface directly.
> Support Custom Properties in Expression Language
> ------------------------------------------------
>
> Key: NIFI-1974
> URL: https://issues.apache.org/jira/browse/NIFI-1974
> Project: Apache NiFi
> Issue Type: New Feature
> Reporter: Yolanda M. Davis
> Assignee: Yolanda M. Davis
> Fix For: 1.0.0
>
>
> Add a property in "nifi.properties" config file to allows users to specify a
> list of custom properties files (containing data such as environmental
> specific values, or sensitive values, etc.). The key/value pairs should be
> loaded upon NIFI startup and availbale to processors for use in expression
> languages.
> Optimally this will lay the groundwork for a UI driven Variable Registry.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
