Matt Burgess created NIFI-5115:
----------------------------------
Summary: Allow scripted controller services to provide their own
properties
Key: NIFI-5115
URL: https://issues.apache.org/jira/browse/NIFI-5115
Project: Apache NiFi
Issue Type: Improvement
Reporter: Matt Burgess
InvokeScriptedProcessor allows the specified script to provide its own
properties, which InvokeScriptedProcessor will ask for when providing all
properties to the user. In this fashion the script can supply additional
properties such as other Controller Services and properties. In contrast,
ExecuteScript only has support for dynamic (i.e. user-defined) properties, as
its script is only evaluated on each run of ExecuteScript.
The scripted Controller Services are currently a hybrid of these two
approaches. They are evaluated ahead of being executed, but they cannot provide
their own properties to the scripted controller service dialog for the user.
One use case is when you have a ScriptedReader that needs to support a Schema
Registry. For a good user experience, the Schema Registry, Name/Text, Access
Strategy properties (for example) should be able to be provided from the script
and displayed to the user in the controller service dialog.
This case tracks the additional capabilities of invoking various configuration
methods on the scripted class as is done with InvokeScriptedProcessor, such as
getSupportedPropertyDescriptors(), validate(), etc.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
