[NIFI-11783] Issue with rollback on retry connection

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.16.0, 1.17.0, 1.16.1, 1.16.2, 1.16.3, 1.18.0, 1.19.0, 1.20.0, 1.19.1, 1.21.0, 1.22.0
• Fix Version/s: 2.0.0-M1, 1.23.0
• Component/s: Core Framework
• Assignee: Mark Payne
• Reporter: Pierre Villard
• Created: 06/Jul/23 17:35
• Updated: 19/Jul/23 19:52
• Resolved: 19/Jul/23 19:52

Description

Consider a GenerateFlowFile -> LookupRecord flow.

The GenerateFlowFile generates a flow file with two records.

The LookupRecord processor is configured with matched/unmatched output relationships.

One of the record is matching an entry in the lookup service, the other record does not match anything.

With default configuration, the FF would be split into one flow file of one record in the matched connection and one flow file of one record in the unmatched relationship.

This is expected behavior.

Now, if I configure the retry mechanism (NIFI-9475) on the unmatched relationship, no flow file is going into the unmatched relationship and I have only one flow file with one record in the matched relationship. We're effectively loosing the records that didn't match anything in the lookup service.

The expected behavior is to have all of the child flow files should be removed and the original flow file should be penalized and rolled back.

Find attached a flow definition to easily reproduce the problem.

Issue Links

• links to: GitHub Pull Request #7500