Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
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.
Attachments
Issue Links
- links to