[ https://issues.apache.org/jira/browse/MINIFI-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15248585#comment-15248585 ]
ASF GitHub Bot commented on MINIFI-12: -------------------------------------- Github user apiri commented on a diff in the pull request: https://github.com/apache/nifi-minifi/pull/13#discussion_r60306850 --- Diff: minifi-nar-bundles/minifi-framework-bundle/minifi-framework/minifi-resources/src/main/resources/conf/bootstrap.conf --- @@ -41,6 +42,11 @@ nifi.minifi.config=./conf/config.yml # How frequently the file specified by 'nifi.minifi.notifier.file.config.path' should be evaluated for changes. #nifi.minifi.notifier.file.polling.period.seconds=5 +# Rest change notifier configuration + +# Port on which the Jetty server will bind to, keep commented for a random open port +#nifi.minifi.notifier.http.port=8338 + --- End diff -- Okay, works for me. > Network based implementation > ---------------------------- > > Key: MINIFI-12 > URL: https://issues.apache.org/jira/browse/MINIFI-12 > Project: Apache NiFi MiNiFi > Issue Type: Sub-task > Components: Data Format, Management, Processing Configuration > Reporter: Aldrin Piri > Assignee: Joseph Percivall > Fix For: 0.0.1 > > > As an initial proof of concept for providing centralized management it would > be advantageous to have configuration move beyond the file descriptor and > start happening from "remote" locations. One way of doing this would be via > simple web service from some control manager to the individual agents. A > preliminary implementation could make use of a REST service to transmit > information and harness the work done in MINIFI-2 as the data format to > transfer the updates to processing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)