[
https://issues.apache.org/jira/browse/NIFI-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16337873#comment-16337873
]
Matt Burgess commented on NIFI-4367:
------------------------------------
Changing the type from Bug to Improvement, as this works as originally
designed. It is unlikely that a scripted processor will be able to function
like a full-fledged native processor, due to differences in the lifecycles,
when methods are called, and which methods can be called externally (such as
getSupportedDynamicProperty()), not to mention annotations (which are not
supported in all programming languages, but see NIFI-2215 which is also an
Improvement). This is why the original design is meant to support scripted
processors that implement Processor and do not extend other base/abstract
classes.
> InvokedScriptedProcessor does not support scripted processor that extends
> AbstractProcessor
> -------------------------------------------------------------------------------------------
>
> Key: NIFI-4367
> URL: https://issues.apache.org/jira/browse/NIFI-4367
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Affects Versions: 1.3.0, 1.4.0, 1.5.0
> Environment: Linux / Windows
> Reporter: Patrice Freydiere
> Priority: Major
> Labels: InvokeScriptedProcessor, validation
>
> InvokeScriptedProcessor pass his ValidationContext to the inner script,
> validate call
> InvokeScriptedProcessor Line 465 : final
> Collection<ValidationResult> instanceResults = instance.validate(context);
>
> The problem is that the invokedscript pass the ScriptFile PropertyDescriptor
> that is validated, if the script derived from the
> AbstractConfigurableComponent, (because the AbstractConfigurableComponent
> validate all the context properties).
> The context should be refined to remove the InvokeScriptedProcessor
> Properties.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
