Closed ihor-sokoliuk-exa closed 1 year ago
That PR was closed due to inactivity, not merged. I'll try to find the right thing, but regardless, that enum is generated by the swagger / openapi, so I think the fix is a new release of nipyapi against the new version
The fix version is 1.14.0
So, nipyapi should have picked this up based on the README version. @Chaffelson ? Any ideas?
@ihor-sokoliuk-exa I have created https://issues.apache.org/jira/browse/NIFI-10207 and will be posting a fix pr. This won't be picked up in nipyapi until there is another nifi release followed by an updated nipyapi release. I don't know if there is any workaround
Thank you, @ottobackwards Will wait for new nifi release
IFF the NiFi API accepts the payload, then we can manually patch the NiPy client to generate it as a workaround. IFF NiFi rejects the payload nothing can be done until a new release.
NiFi accepts the payload.
The PR has landed, this should be in the next release
Hi @ottobackwards @Chaffelson Great news! NiFi 1.17.0 version was released a few days ago. And your changes are in there already.
Do you have any plans for a new nipyapi release?
That is up to @Chaffelson,
Investigating now
Description
NiFi has added a RUN_ONCE state for a processor. https://github.com/apache/nifi/pull/1458/files But nipyapi lib doesn't support it. As a result, it fails when trying to get a processor/process group that was started with the Run once option.
What I Did
Just run
nipyapi.canvas.get_process_group(identifier=pg_name, identifier_type='name')
when there is at least one processor in the RUN_ONCE state. For example, run once the ExecuteStreamCommand that runs the pythons script where it gathers the processor that runs this script.Urgency
It is not blocking so much in automated flows, but it blocks debugging sometimes.