[ https://issues.apache.org/jira/browse/MINIFI-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15237735#comment-15237735 ]
ASF GitHub Bot commented on MINIFI-2: ------------------------------------- Github user JPercivall commented on a diff in the pull request: https://github.com/apache/nifi-minifi/pull/7#discussion_r59429946 --- Diff: minifi-api/src/main/java/org/apache/nifi/minifi/configuration/ConfigurationChangeNotifier.java --- @@ -21,6 +21,11 @@ public interface ConfigurationChangeNotifier { /** + * Begins the associated notification service provided by the given implementation. In most implementations, no action will occur until this method is invoked. + */ + void initialize(); --- End diff -- That works for me > File based implementation > ------------------------- > > Key: MINIFI-2 > URL: https://issues.apache.org/jira/browse/MINIFI-2 > Project: Apache NiFi MiNiFi > Issue Type: Sub-task > Components: Processing Configuration > Reporter: Aldrin Piri > Fix For: 0.0.1 > > Attachments: ConfigFileExplanation.xml, Properties_Guide.md, > config.yml > > > A defined schema for processing configuration will need to be defined. XML > or YAML seem like possible options for achieving this. > Agent configuration will come from two places, a bootstrap properties file > and a flow configuration file. The bootstrap will make use of some of the > original nifi.properties in order to start up the agent. The flow > configuration file will essentially be a stripped down version of a flow.xml > (with potentially S2S properties from nifi.properties). > The format for the bootstrap.properties should likely be similar to > nifi.properties. > Further, a way to incorporate this to leverage the libraries from core NiFi > will aid in achieving a proof of concept implementation more expediently. -- This message was sent by Atlassian JIRA (v6.3.4#6332)