[jira] [Commented] (NIFI-14266) Allow ExecuteSQL to not overwrite flowfile content when no result

["ASF subversion and git services (Jira)" <ji...@apache.org>]

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

ASF subversion and git services commented on NIFI-14266:
--------------------------------------------------------

Commit 8e52d9c53d1b556482d278bb61227a971972625b in nifi's branch refs/heads/NIFI-14266 from Pierre Villard
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=8e52d9c53d ]

NIFI-14266 - Allow ExecuteSQL to not overwrite flowfile content when no result


> Allow ExecuteSQL to not overwrite flowfile content when no result
> -----------------------------------------------------------------
>
>                 Key: NIFI-14266
>                 URL: https://issues.apache.org/jira/browse/NIFI-14266
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Pierre Villard
>            Assignee: Pierre Villard
>            Priority: Major
>
> The ExecuteSQL processor may be used in a flow definition to execute SQL statements such as TRUNCATE TABLE, DROP TABLE, etc. While there is the option to use pre/post queries, it might not always be an option to have everything executed within the same processor. In such a scenario, it might be needed to not change the content of the FlowFile.
> This improvement adds a property allowing a user to specify that the FlowFile's content should remain untouched when the execution of the query does not generate any result and, of course, when the processor was triggered by an incoming FlowFile.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)