[
https://issues.apache.org/jira/browse/NIFI-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15866162#comment-15866162
]
ASF GitHub Bot commented on NIFI-3432:
--------------------------------------
Github user patricker commented on a diff in the pull request:
https://github.com/apache/nifi/pull/1471#discussion_r101090904
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/test/java/org/apache/nifi/processors/standard/TestExecuteSQL.java
---
@@ -222,7 +222,10 @@ public void testWithSqlException() throws SQLException
{
runner.setProperty(ExecuteSQL.SQL_SELECT_QUERY, "SELECT val1 FROM
TEST_NO_ROWS");
runner.run();
- runner.assertAllFlowFilesTransferred(ExecuteSQL.REL_FAILURE, 1);
+ //No incoming flow file containing a query, and an exception
causes no outbound flowfile.
+ // There should be no flow files on either relatationship
+ runner.assertTransferCount(ExecuteSQL.REL_FAILURE, 0);
+ runner.assertTransferCount(ExecuteSQL.REL_FAILURE, 0);
--- End diff --
Yep, it's fixed now.
> ExecuteSQL Should Support Multiple ResultSets
> ---------------------------------------------
>
> Key: NIFI-3432
> URL: https://issues.apache.org/jira/browse/NIFI-3432
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Core Framework
> Affects Versions: 1.2.0
> Reporter: Peter Wicks
> Assignee: Peter Wicks
> Priority: Minor
> Fix For: 1.2.0
>
>
> ExecuteSQL processor only supports processing a single resultset. If a
> query/stored procedure call returns multiple resultsets then only one is kept.
> ExecuteSQL should be updated to support handling multiple resultsets. When
> multiple resultsets exist a flow file should be created for each resultset.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
