I'm using nifi-swagger-client:1.3.0.0 and FlowApi.scheduleComponents to run a processor group.
Processor group contains a lot of processor and processor groups as well
With the attached code i get a valid response but processor group does't start in NIFI.
I noted that if I add all components in body object it works fine.
As documentation stated "If the components in the request are not specified, all authorized components will be considered" so the expected behaviour is processor group should be started
Configuration.setDefaultApiClient(client)
val apiInstance: FlowApi = new FlowApi()
val id = "21394497-5350-1357-0000-000075670e88"
val body : ScheduleComponentsEntity = new ScheduleComponentsEntity()
body.setId(id)
val status = ScheduleComponentsEntity.StateEnum.RUNNING
body.setState(status)
vall result = apiInstance.scheduleComponents(id,body)`
I'm using nifi-swagger-client:1.3.0.0 and FlowApi.scheduleComponents to run a processor group. Processor group contains a lot of processor and processor groups as well
With the attached code i get a valid response but processor group does't start in NIFI. I noted that if I add all components in body object it works fine.
As documentation stated "If the components in the request are not specified, all authorized components will be considered" so the expected behaviour is processor group should be started
`val client: ApiClient = new ApiClient().setBasePath("http://localhost:10135/nifi-api")
Configuration.setDefaultApiClient(client) val apiInstance: FlowApi = new FlowApi() val id = "21394497-5350-1357-0000-000075670e88" val body : ScheduleComponentsEntity = new ScheduleComponentsEntity() body.setId(id) val status = ScheduleComponentsEntity.StateEnum.RUNNING body.setState(status) vall result = apiInstance.scheduleComponents(id,body)`