[
https://issues.apache.org/jira/browse/NIFI-14266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17930735#comment-17930735
]
ASF subversion and git services commented on NIFI-14266:
--------------------------------------------------------
Commit 70cd51ce700013cda861b1560d05df38df74dfeb in nifi's branch
refs/heads/main from Marcin Gemra
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=70cd51ce70 ]
NIFI-14266 Added Content Output Strategy property to ExecuteSQL (#9748)
- Content Output Strategy supports current behavior of writing an empty result
set when the query returns no results, and also supports retaining the original
content for input FlowFiles
Co-authored-by: Marcin Gemra <[email protected]>
Co-authored-by: Pierre Villard <[email protected]>
Co-authored-by: David Handermann <[email protected]>
Signed-off-by: David Handermann <[email protected]>
> 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
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> 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)
