You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Joseph Percivall (JIRA)" <ji...@apache.org> on 2017/01/26 20:42:24 UTC
[jira] [Resolved] (NIFI-3044) Execute Script Ruby Libraries
[ https://issues.apache.org/jira/browse/NIFI-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joseph Percivall resolved NIFI-3044.
------------------------------------
Resolution: Not A Bug
This is not a bug in NiFi but is due to the default configuration of JRuby as explained in NIFI-3406. If NiFi is not restarted then changing the libs would not matter as the Runtime has already been initialized.
In order to provide a better ExecuteScript UX (and avoid this issue) more configuration for the different Script Engines should be exposed.
> Execute Script Ruby Libraries
> ------------------------------
>
> Key: NIFI-3044
> URL: https://issues.apache.org/jira/browse/NIFI-3044
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Justin M Cavinee
> Priority: Minor
>
> ExecuteScript appears to cache required classes, even when they've been updated.
> I have a shared library for interfacing with one of our web services, which several different scripts use (it implements a class, that gets imported by the other scripts). After using for a couple of days, I found a bug in the library, so I updated it, but noticed the fix was not being picked up by my execute script processors (even after restarting the processors). It wasn't until I renamed the file / class, and updated my require statement in my other scripts that the update was picked up.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)