[ 
https://issues.apache.org/jira/browse/MINIFICPP-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Debreceni updated MINIFICPP-1270:
--------------------------------------
    Description: 
There is already a feedback on update failures in \{{C2Agent.cpp}}
{code:java}
C2Payload response(Operation::ACKNOWLEDGE, state::UpdateState::SET_ERROR, 
resp.ident, false, true);
response.setRawData("Error while applying flow. Likely missing 
processors");{code}
but it is quite sparse, as `StateMonitor::applyUpdate` does not provide proper 
feedback.

 

We should introduce a new `applyUpdateWithFeedback` (subject to change), which 
also takes an `UpdateErrorReporter` and propagate this through so that the 
eventual verification step can fill it properly. 

  was:
There is already a feedback on update failures in `C2Agent.cpp`
{code:java}
C2Payload response(Operation::ACKNOWLEDGE, state::UpdateState::SET_ERROR, 
resp.ident, false, true);
response.setRawData("Error while applying flow. Likely missing 
processors");{code}
but it is quite sparse, as `StateMonitor::applyUpdate` does not provide proper 
feedback.

 

We should introduce a new `applyUpdateWithFeedback` (subject to change), which 
also takes an `UpdateErrorReporter` and propagate this through so that the 
eventual verification step can fill it properly. 


> Notify C2Agent of the cause of configuration update failure
> -----------------------------------------------------------
>
>                 Key: MINIFICPP-1270
>                 URL: https://issues.apache.org/jira/browse/MINIFICPP-1270
>             Project: Apache NiFi MiNiFi C++
>          Issue Type: Improvement
>            Reporter: Adam Debreceni
>            Priority: Major
>
> There is already a feedback on update failures in \{{C2Agent.cpp}}
> {code:java}
> C2Payload response(Operation::ACKNOWLEDGE, state::UpdateState::SET_ERROR, 
> resp.ident, false, true);
> response.setRawData("Error while applying flow. Likely missing 
> processors");{code}
> but it is quite sparse, as `StateMonitor::applyUpdate` does not provide 
> proper feedback.
>  
> We should introduce a new `applyUpdateWithFeedback` (subject to change), 
> which also takes an `UpdateErrorReporter` and propagate this through so that 
> the eventual verification step can fill it properly. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to