You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Malthe Borch (Jira)" <ji...@apache.org> on 2020/07/23 12:00:00 UTC

[jira] [Created] (NIFI-7666) Allow parametrizing SQL statements based on custom processor fields

Malthe Borch created NIFI-7666:
----------------------------------

             Summary: Allow parametrizing SQL statements based on custom processor fields
                 Key: NIFI-7666
                 URL: https://issues.apache.org/jira/browse/NIFI-7666
             Project: Apache NiFi
          Issue Type: New Feature
            Reporter: Malthe Borch


Today, query processors such as ExecuteSQL allow parametrized SQL statements based on incoming flow file attributes on the form "sql.args.N.{type;value;format}".

This is a proposal to add a secondary mode where these parameters are drawn instead from custom properties.

When the secondary mode (i.e. "Use custom properties to set parameters") is enabled, custom properties are used instead of flow file attributes.

* The NiFi Expression Language can be used in these properties (will be evaluated using flow file attributes and variable registry).
* In addition to "sql.args.N.value" there will be a sensitive version "sql.args.N.sensitive". It's an error to provide both.

That is, in addition to providing improved ergonomics (allowing the processor to control the parameters, possibly drawing from more human-friendly attribute names), this also enables the use of sensitive properties. As a specific example, a database can have a "COPY INTO" statement which supports the ingestion of data from blob storage requiring an authentication token.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)