[
https://issues.apache.org/jira/browse/NIFI-6852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17012927#comment-17012927
]
Mark Bean commented on NIFI-6852:
---------------------------------
This issue also presents itself for another use case: a controller service that
includes dynamic properties where that property is another controller service
(i.e. ControllerService.class).
Prior to 1.10.0, referenced controller services in dynamic properties were not
validated against an API. NIFI-6798 fixed that. Therefore, a (custom)
controller service which validated pre-1.10.0 no longer validates.
I don't see a downside to allowing all ControllerService.class API components
to validate as long as the designer intends to allow ANY controller service. In
certain cases, this is required.
> CTL doesn't work in ExecuteGroovyScript processor with Apache NiFi 1.10.0
> -------------------------------------------------------------------------
>
> Key: NIFI-6852
> URL: https://issues.apache.org/jira/browse/NIFI-6852
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.10.0
> Reporter: Behrouz
> Assignee: Shawn Weeks
> Priority: Blocker
> Attachments: NIFI_CTL.png
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> more information is available in this stackoverflow question:
> [https://stackoverflow.com/questions/58731092/why-ctl-doesnt-work-in-executegroovyscript-processor-with-apache-nifi-1-10-0]
> according to daggett comment in stackoverflow the source of error seems to be
> [https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core-api/src/main/java/org/apache/nifi/controller/AbstractComponentNode.java#L746|http://example.com/]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
