[ https://issues.apache.org/jira/browse/NIFI-7444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17226838#comment-17226838 ]
Rahul Soni commented on NIFI-7444: ---------------------------------- I agree to you POV [~markap14]. In my opinion this is a big improvement that we should make to NiFi processors, wherever applicable. I have now seen a few clients who have struggled with this implementation, or rather lack of it. Would be more than happy to discuss it further. > Add "retry" relation to the Convert Record Processor > ---------------------------------------------------- > > Key: NIFI-7444 > URL: https://issues.apache.org/jira/browse/NIFI-7444 > Project: Apache NiFi > Issue Type: New Feature > Components: Configuration > Reporter: Rahul Soni > Priority: Minor > > Follows the case for adding a retry relationship and redirect the "failed" > conversion to this relationship in certain scenarios with one of those > discussed below. > Today we have either success or failure relationship for ConvertRecord > processor. It works well until the Record Reader/Writer is using Schema > Registry and then we reach a point where Schema Registry is unavailable due > to any reason. Now the records which are supposed to be converted from one > format to another are routed to failure because “schema” is not found for > those flow files. > One can re-attempt those flow files in one way or another but the issue is > it’s not effective to retry a flow file any number of times which doesn’t > have a schema available, actually. On the flip side, we can have a counter > that the flow file should be tried n number of times before being redirected > to the failure relationship but then again we are on the mercy of Schema > Registry to be up within the configured period of re-attempts before we > potentially "lose" the flow file by redirecting it to the failed relationship. > -- This message was sent by Atlassian Jira (v8.3.4#803005)