Actually, I suspect the export from nifi is supposed to be
scheduledState: Enabled.
I think its probably the job of the minifi-toolkit to change that from
Enabled to Running.
On 20/1/2025 5:07 pm, Robert Cohen wrote:
OK, I believe Ive spotted the problem with exporting code from nifi
2.1.0 to minifi 2.1.0
I have 2 minifi 2.1.0 flow.json.raw files.
The first came from nifi 2.1.0 and converted with minifi-toolkikt
transform-nifi.
The second came from minifi 1.28.1 converted with minifi-toolkit
transform-yml
The code that came from minifi works. The code that comes from nifi
doesnt.
Comparing the two, I spotted a difference.
For the remote process groups, in the working code, the input ports
have "scheduledState": "RUNNING",
For the non working code that came from nifi, the remote process
groups have input ports with "scheduledState": "ENABLED",
If I take the nifi output and change the scheduledState to Running,
the code then works.
I checked the exported file coming from nifi, to see if the problem
was with the nifi export or in the converter.
The problem is there in the exported file. So it appears to be a nifi
problem, not a toolkit problem.
