[
https://issues.apache.org/jira/browse/NIFI-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15082370#comment-15082370
]
Joseph Witt commented on NIFI-684:
----------------------------------
Hello Sumo. Just wanted to make sure you saw Matt's note on Dec 2 about this.
http://mail-archives.apache.org/mod_mbox/nifi-dev/201512.mbox/%3C7844597F-0B34-4FF1-A014-8C573B5ECD4E%40gmail.com%3E
It looks like his NIFI-210 patch is close which includes Groovy. Just want to
make sure your ideas/interests were covered there as well.
Thanks
Joe
> ExecuteGroovy proof of concept
> --------------------------------
>
> Key: NIFI-684
> URL: https://issues.apache.org/jira/browse/NIFI-684
> Project: Apache NiFi
> Issue Type: Task
> Components: Extensions
> Reporter: Ricky Saltzer
> Assignee: Ricky Saltzer
> Labels: dynamic_language
> 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)
