[
https://issues.apache.org/jira/browse/MINIFI-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15244683#comment-15244683
]
ASF GitHub Bot commented on MINIFI-14:
--------------------------------------
Github user apiri commented on a diff in the pull request:
https://github.com/apache/nifi-minifi/pull/10#discussion_r59985963
--- Diff:
minifi-nar-bundles/minifi-framework-bundle/minifi-framework/minifi-resources/src/main/resources/conf/bootstrap.conf
---
@@ -28,6 +28,16 @@ conf.dir=./conf
# How long to wait after telling MiNiFi to shutdown before explicitly
killing the Process
graceful.shutdown.seconds=20
+# The location for the configuration file
+nifi.minifi.config=./conf/config.yml
+
+# Notifiers to use for the associated agent, comma separated list of class
names
+#nifi.minifi.notifier.components=org.apache.nifi.minifi.bootstrap.configuration.FileChangeNotifier
+
+# File change notifier configuration for path of the file to monitor and
the associated polling period
+#nifi.minifi.notifier.file.config.path=
--- End diff --
Yep, we can adjust. It's just a matter of how we convey to the listener
that there is not an input stream/file such that the listener shouldn't save.
Let me refactor a bit and push another commit out.
> Add Listener/Notifier Logic to RunMiNiFi
> ----------------------------------------
>
> Key: MINIFI-14
> URL: https://issues.apache.org/jira/browse/MINIFI-14
> Project: Apache NiFi MiNiFi
> Issue Type: Sub-task
> Components: Processing Configuration
> Reporter: Joseph Percivall
> Assignee: Aldrin Piri
> Fix For: 0.0.1
>
>
> The interface for the ConfigurationChangeNotifier and
> ConfigurationChangeListener is done as part of MINIFI-4 but configuration and
> implementation in RunMiNiFi needs to be added.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
