[
https://issues.apache.org/jira/browse/NIFI-3688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15969892#comment-15969892
]
ASF GitHub Bot commented on NIFI-3688:
--------------------------------------
Github user dlukyanov commented on the issue:
https://github.com/apache/nifi/pull/1662
@joewitt , about naming: CallGroovy would be fine?
Actually it's another implementation of groovy script.
And the Script processor is just a Script - and not CallScript.
I wanted to point that it's extended groovy script.. What do you think
about the name?
> Create extended groovy scripting processor
> ------------------------------------------
>
> Key: NIFI-3688
> URL: https://issues.apache.org/jira/browse/NIFI-3688
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Reporter: Dmitry Lukyanov
> Priority: Minor
>
> The idea is to simplify groovy scripting.
> Main targets:
> - to be compatible with existing groovy scripting
> - simplify read/write attributes
> - simplify read/write content
> - avoid closure casting to nifi types like `StreamCallback`
> - simplify and provide visibility when accessing to controller services from
> script
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
