nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NIFI-3432) ExecuteSQL Should Support Multiple ResultSets
Date Wed, 15 Feb 2017 04:21:41 GMT

    [ https://issues.apache.org/jira/browse/NIFI-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15867210#comment-15867210
] 

ASF GitHub Bot commented on NIFI-3432:
--------------------------------------

Github user mattyb149 commented on the issue:

    https://github.com/apache/nifi/pull/1471
  
    I just noticed in the added unit test that one of the examples of a "query" that returns
no ResultSets is an "UPDATE". Are you proposing that ExecuteSQL be able to handle these kinds
of statements? In my experience, PutSQL is used for these kinds of statements. Do you see
ExecuteSQL needing to be able to handle these as well? If so, can you describe a use case?


> 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)

Mime
View raw message