Matt Gilman commented on NIFI-4900:

The components field is used to indicate which components should be scheduled. 
The reason this exists is that only the components the current user has access 
to are eligible to be scheduled. Since the Authorizer is an extension point, 
there is no guarantee that each node would schedule the same set of components. 
To prevent this potential dataflow inconsistency, the node that receives the 
request will determine the components that it thinks are eligible for 
scheduling. This set of components is then replicated across the cluster using 
a two-phase commit to ensure all nodes attempt to operate on the same 
components. Because this field is meant for input to the endpoint, it only 
contains the component identifier and its current revision.

If this Jira is meant to include some output, please use a separate field and 
make it optionally populated. Some clients do not care for those details which 
could be quite large since the number of scheduled components is technically 

> 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

Reply via email to