[
https://issues.apache.org/jira/browse/NIFI-9967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544534#comment-17544534
]
Fabio Coutinho commented on NIFI-9967:
--------------------------------------
[~mattyb149] hello! I have just tried out MiNiFi and the issue was indeed
solved. I have however run into another problem.
I have setup a MiNiFi agent connecting to a C2 using PullHttpChangeIngestor and
the C2 is connected to a central NiFi server. When I create a new template (for
instance changing to .v1 to .v2) everything works out fine and the MiNiFi agent
reloads the config and starts the new flow (.v2 in this example) as expected.
However the MiNiFi stops querying the C2 for new changes.
Once I restart the MiNiFi agent process, it starts polling again against
changes. Do you have this problem as well? Any idea on how to fix this issue?
> MiNiFi doesn't pick up config.yml changes
> -----------------------------------------
>
> Key: NIFI-9967
> URL: https://issues.apache.org/jira/browse/NIFI-9967
> Project: Apache NiFi
> Issue Type: Bug
> Components: MiNiFi
> Reporter: Matt Burgess
> Assignee: Matt Burgess
> Priority: Major
> Fix For: 1.17.0, 1.16.2
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> MiNiFi is still coded to overwrite flow.xml.gz from config.yml before it
> restarts. But it uses NiFi’s flow loading code so as of NIFI-9069 it
> generates (and looks first for) a flow.json.gz. That means once you start up
> MiNiFi, you have to manually delete flow.json.gz before it will recognize any
> changes made to config.yml.
> MiNiFi should instead create/overwrite the flow.json.gz file.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
