Hi Pushkar, you can automatically update the MiniFi configs using one of three methods:
* FileChangeIngestor * RestChangeIngestor * PullHttpChangeIngestor You have to configure the MiNiFi bootstrap.conf. Here you can read how to do this: https://nifi.apache.org/minifi/system-admin-guide.html To update the MiNiFi config you have to create a Process Group (at NiFi UI) where you define the MiNiFi workflow. Save the Process Group as template. Export the template and convert it to MiNiFi config.yml by using the MiNiFi Toolkit (https://nifi.apache.org/minifi/download.html). Hot to transform the template to config.yml? Change to MINIFI_TOOLKIT_HOME and type: /bin/config.sh transform [PATH_TO_TEMPLATE_FILE/TEMPLATE_FILE_NAME] [PATH_TO_CONFIG_GFILE/CONFIG_FILE_NAME] You don't need to stop anything. If MiNiFi gets a new config then it checks validity and restarts itself. Best Regards, Uwe Moosheimer Am 31.01.2017 um 19:00 schrieb Pushkara R: > Hi, > > I am a part of a Research Lab in Indian Institute of Science and we are > currently evaluating MiNiFi as candidate for out IoT deployments. There are > two things I wanted get clarified as I could not find relavant > documentation. > > 1. It is mentioned in multiple places that using NiFi we can update the > processor Topology of multiple instances of MiNiFi that are connected to > it. However, I am not able to figure out how. I assume it would involve > communication with the MiNiFi bootstrap and passing it the relavant yml > file, but I don't know how to do it. Could someone please elaborate? > > 2. On NiFi, the processor topology can be updated in the UI without > stopping the entire topology. Only the concerned processors need to be > stopped. Though MiNiFi does not have a UI, is it necessary that every minor > edit to the topology needs a restart? Is there a way to go around the > necessity to restart MiNiFi entirely? > > Regards > Pushkar >
