[
https://issues.apache.org/jira/browse/NIFI-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16370657#comment-16370657
]
Patrice Freydiere commented on NIFI-4367:
-----------------------------------------
Hi sorry for the lake of response, i was very busy thoses last days, and 'll
have the time to take consideration on this fix and quitely have a deep
understanding on it.
[~mattyb149] : yes you're right, it not a complete full processor
implementation, but it is a lean path for full fledge production proof
processor implementation.
on our side in France IT, nifi gain into consideration, and scripting
capabilities really ease the process into a production proof dataflow. Thanks
for your work it really help.
> 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: Extensions
> 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)
