You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/12/12 01:37:00 UTC
[jira] [Commented] (NIFI-4561) ExecuteSQL Stopped Returning
FlowFile for non-ResultSet Queries
[ https://issues.apache.org/jira/browse/NIFI-4561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16286943#comment-16286943 ]
ASF GitHub Bot commented on NIFI-4561:
--------------------------------------
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/2243
@patricker I'll try to take a look at this soon
> ExecuteSQL Stopped Returning FlowFile for non-ResultSet Queries
> ---------------------------------------------------------------
>
> Key: NIFI-4561
> URL: https://issues.apache.org/jira/browse/NIFI-4561
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Peter Wicks
> Assignee: Peter Wicks
>
> While most people use ExecuteSQL for Select statements, some JDBC drivers allow you to execute any kind of statement, including multi-statement requests.
> This allowed users to submit multiple SQL statements in one JDBC Statement and get back multiple result sets. This was part of the reason I wrote [NIFI-3432].
> After having NIFI-3432 merged, I found that some request types no longer cause a FlowFile to be generated because there is no ResultSet. Also, if request types are mixed, such as an insert followed by a Select, then no ResultSet is returned because the first result is not a result set but an Update Count.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)