[
https://issues.apache.org/jira/browse/NIFI-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15005595#comment-15005595
]
Aldrin Piri commented on NIFI-684:
----------------------------------
Hey guys,
Sorry for not following up sooner. Have to tune my inbox filters!
I would say given where we currently stand in driving toward a release we defer
this one to 0.5.0 and give this an appropriate amount of diligence in the
design and implementation of it. This among the other dynamic processors would
be nice to tackle "at once" to get some good consistency across their breadth
of offerings.
Will try to link all these dynamic language items together for cohesion
> ExecuteGroovy proof of concept
> --------------------------------
>
> Key: NIFI-684
> URL: https://issues.apache.org/jira/browse/NIFI-684
> Project: Apache NiFi
> Issue Type: Task
> Reporter: Ricky Saltzer
> Assignee: Ricky Saltzer
> Attachments: ExecuteGroovy.java, TestExecuteGroovy.java,
> TestScript.groovy
>
>
> Following up on the email thread which described using a dynamic language to
> execute code, rather than requiring a custom NAR to be created each time.
> Using this JIRA to track some prototype code I wrote to allow Groovy to
> execute code inside a processor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
