[
https://issues.apache.org/jira/browse/NIFI-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16375059#comment-16375059
]
Daniel Chaffelson commented on NIFI-4900:
-----------------------------------------
Thanks for the detailed explanation [~mcgilman]
This makes sense, in that the field is essentially for submission control only.
It is not difficult to implement a wait loop for the components to achieve the
submitted state or timeout, which is ultimately what I've done in my Python
Client SDK.
I think, from your description, that this isn't a bug and also isn't really
worth being a feature either, so unless someone else feels invested in the idea
I'll close it.
> nifi Swagger definition - FlowApi ScheduleComponents returns empty component
> list
> ---------------------------------------------------------------------------------
>
> Key: NIFI-4900
> URL: https://issues.apache.org/jira/browse/NIFI-4900
> Project: Apache NiFi
> Issue Type: Bug
> Components: SDLC
> Affects Versions: 1.5.0
> Reporter: Daniel Chaffelson
> Priority: Minor
>
> When issuing a command to Schedule Components with the 'components' attribute
> set, the command returns an empty set back. This seems incongruous. I would
> expect to receive back an object listing out the states of each component
> that the scheduling command was issued against so I can tell which components
> where operated upon.
> This can be reproduced by creating two processors within a process group, and
> issuing a schedule component command with a component attribute referencing
> only one of the processors, which will then change scheduled state leaving
> the other as-was. It evidences that the individual component request is being
> honoured, but the return from the API is the same as if all components in the
> process group had been scheduled.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
