[
https://issues.apache.org/jira/browse/NIFI-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15867232#comment-15867232
]
ASF GitHub Bot commented on NIFI-3432:
--------------------------------------
Github user patricker commented on the issue:
https://github.com/apache/nifi/pull/1471
@mattyb149 I generally use ExecuteSQL to call Stored Procedures.
Unfortunately Stored Procedures are such a pain in Derby it was easier to build
a test that called an update statement.
However, I have already used ExecuteSQL for Inserts in the past without
issue and without modification. I didn't really even think about using PutSQL
since it was a single record I was inserting for tracking metrics in an
external reporting database.
> 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)
