You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Jason Carey (JIRA)" <ji...@apache.org> on 2015/01/02 08:17:13 UTC

[jira] [Commented] (NIFI-210) Scala Support for ExecuteScript Processor

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

Jason Carey commented on NIFI-210:
----------------------------------

I spent some time on this, and I have not been able to get support for Scala scripting working in conjunction with the other supported languages.  It seems there is a classpath issue when evaluating Scala scripts that conflicts with subsequent JavaScript evaluations.  I noticed this while writing unit tests.  Interestingly, I have not been able to reproduce the issue with jython or jruby.  Unit tests for each language run correctly in isolation.  The root cause is still not clear.

I may be able to get some help from the community, but at this point since you marked this ticket as major, you may want to write a processor that calls your Scala code or implement everything in Java.

Note that I was unable to push my branch to origin due to authentication failures.  I'll update this ticket when my branch is pushed at which point the test failures will highlight the described classpath issue.



> Scala Support for 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: Jason Carey
>              Labels: processor, scala
>
> Add latest Scala version support for ExcecuteScript processor.



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