You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Andrew Grande (JIRA)" <ji...@apache.org> on 2015/11/07 23:18:10 UTC
[jira] [Commented] (NIFI-684) ExecuteGroovy proof of concept
[ https://issues.apache.org/jira/browse/NIFI-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995425#comment-14995425 ]
Andrew Grande commented on NIFI-684:
------------------------------------
What's the relationship with NIFI-935? IMO, we should be using standard Java dynamic scripts bindings and not implementation-specific. Two more notes:
# Provide a way to paste the script inline - it can get very difficult deploying scripts to multiple nodes, and current implementation references an external file only.
# The script must be precompiled and stored on processor's initialization, not re-evaluated on every invocation.
My only concern is if this one gets added, then jython, then refactoring is due and people start mentioning this original implementation as a 'must-have' for backwards compatibility.
> 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)