Matt Burgess created NIFI-5553:
----------------------------------
Summary: ExecuteSQL incorrectly causes session rollback rather
than routing to failure
Key: NIFI-5553
URL: https://issues.apache.org/jira/browse/NIFI-5553
Project: Apache NiFi
Issue Type: Bug
Components: Extensions
Reporter: Matt Burgess
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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
