[
https://issues.apache.org/jira/browse/NIFI-13541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17868655#comment-17868655
]
ASF subversion and git services commented on NIFI-13541:
--------------------------------------------------------
Commit dca7aac9b3f3b9e79ed37572d17f69c89d295470 in nifi's branch
refs/heads/main from Ferenc Kis
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=dca7aac9b3 ]
NIFI-13541 [MiNiFi] Validate flow during startup
Signed-off-by: Csaba Bejan <[email protected]>
This closes #9073.
> [MiNiFi] Prevent flows to start with validation errors
> ------------------------------------------------------
>
> Key: NIFI-13541
> URL: https://issues.apache.org/jira/browse/NIFI-13541
> Project: Apache NiFi
> Issue Type: Improvement
> Components: MiNiFi
> Affects Versions: 2.0.0-M4
> Reporter: Ferenc Kis
> Assignee: Ferenc Kis
> Priority: Major
> Labels: minifi-java
> Fix For: 2.0.0-M5
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> * currently in C2 Update/Configuration we have a piece of logic which detects
> validation errors in the flow after the update, and reverts the change if any
> issues
> * this is beneficial as it informs the C2 server that the flow update was not
> successful and won't leave the agent in an inconsistent state
> * in the non C2 program flow there is no such check, so flows can start with
> validation errors, without any notification
> * this is non beneficial, as unlike NiFi, MiNiFi does not have a UI where the
> validation information is displayed and the flow can be changed in case of
> any issues
> * in case of MiNiFi we should only allow flows without any validation errors
> to run, and prevent the flow to start if any validation error occurs
> * also the user should be notified via the logs with the detailed message of
> the validation errors
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
