[NIFI-5553] ExecuteSQL incorrectly causes session rollback rather than routing to failure

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.8.0
• Component/s: Extensions
• Assignee: Matt Burgess
• Reporter: Matt Burgess
• Created: 24/Aug/18 17:29
• Updated: 29/Aug/18 11:27
• Resolved: 29/Aug/18 11:27

Description

If ExecuteSQL has an incoming connection and the query executes successfully, then if an error occurs while processing the result set(s), the session incorrectly gets rolled back, when the expected behavior is to route the incoming flow file to failure.

After the query executes successfully, a flow file is created to contain the result set.If an exception occurs after this, the original incoming flow file is correctly transferred to failure, but the result set flow file has not been removed. This causes the session to rollback and thus return the incoming flow file to the incoming queue.

This has been verified as a bug in NiFi 1.5.0 and the current master (1.8.0-SNAPSHOT) but is working as expected in NiFi 1.2.0. I suspect this may have been introduced by NIFI-3432, in any case a unit test should be added to prevent regressions.

Issue Links

• links to: GitHub Pull Request #2967