You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@nifi.apache.org by "Aldrin Piri (JIRA)" <ji...@apache.org> on 2015/11/14 21:31:11 UTC

[jira] [Updated] (NIFI-684) ExecuteGroovy proof of concept

     [ https://issues.apache.org/jira/browse/NIFI-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aldrin Piri updated NIFI-684:
-----------------------------
    Labels: dynamic_language  (was: )

> 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)