[ 
https://issues.apache.org/jira/browse/NIFI-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15117464#comment-15117464
 ] 

ASF GitHub Bot commented on NIFI-210:
-------------------------------------

GitHub user mattyb149 reopened a pull request:

    https://github.com/apache/nifi/pull/185

    NIFI-210: Add ExecuteScript and InvokeScriptProcessor

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mattyb149/nifi script-processors

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/185.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #185
    
----
commit 0d869899fb2f50f2845c9f1ce0e05e12d40d9c47
Author: Matt Burgess <[email protected]>
Date:   2016-01-25T21:58:23Z

    NIFI-210: Add ExecuteScript and InvokeScriptProcessor

----


> Provide an ExecuteScript processor
> ----------------------------------
>
>                 Key: NIFI-210
>                 URL: https://issues.apache.org/jira/browse/NIFI-210
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>    Affects Versions: 0.0.1
>            Reporter: A. Steven Anderson
>            Assignee: Matt Burgess
>              Labels: processor, scala
>             Fix For: 0.5.0
>
>         Attachments: 
> 0001-NIFI-210-few-tweaks-to-drop-static-reference-and-fix.patch
>
>
> Add latest Scala version support for ExcecuteScript processor.
> Should also support Clojure as per discussion and request on mailing list 
> http://mail-archives.apache.org/mod_mbox/nifi-dev/201506.mbox/%3CCAMpSqch4GK1gnw6M1u8tH6AN8e_miXZN5SNkAeMjBujXYGqJiw%40mail.gmail.com%3E
> UPDATE: The ScriptEngine for Clojure is not being maintained and is not 
> currently available via Maven Central or a public repository. Recommend 
> adding Clojure as a separate Improvement Jira case.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to