[
https://issues.apache.org/jira/browse/NIFI-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16221848#comment-16221848
]
ASF subversion and git services commented on NIFI-4522:
-------------------------------------------------------
Commit 856dedab122f767cf52b18d28b0adf3ba3c09c70 in nifi's branch
refs/heads/master from [~ca9mbu]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=856deda ]
NIFI-4522: Add SQL Statement property to PutSQL
Signed-off-by: Pierre Villard <[email protected]>
This closes #2225.
> Add "SQL Statement" property to PutSQL
> --------------------------------------
>
> Key: NIFI-4522
> URL: https://issues.apache.org/jira/browse/NIFI-4522
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Matt Burgess
> Assignee: Matt Burgess
> Fix For: 1.5.0
>
>
> Currently the PutSQL processor expects the SQL statement to be executed to be
> in the contents of the incoming flow file(s). However there is a use case
> from a Simple Event Processing perspective; when you have a flowfile whose
> contents you want to keep, but because that flow file came through
> (presumably with some attributes of interest), you want to issue a SQL
> statement (perhaps to update an external DB with some status/metrics info).
> Adding a non-required, expression-language-supported, default-empty property
> called SQL Statement would allow both use cases; it preserves existing
> behavior by default, but provides the ability to issue an external command
> while retaining the current flow file contents.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
