[
https://issues.apache.org/jira/browse/NIFI-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ricky Saltzer updated NIFI-684:
-------------------------------
Attachment: TestScript.groovy
TestExecuteGroovy.java
ExecuteGroovy.java
[~joewitt]
Uploading some of the proof of concept code for a processor that can execute
code dynamically, while still keeping the same level of API completeness using
Groovy.
Worked reasonably well for me, I'm not currently sure of the performance impact
of using something like this, though.
> 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)
