You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "marco polo (JIRA)" <ji...@apache.org> on 2017/11/17 02:29:00 UTC
[jira] [Commented] (MINIFICPP-308) Script objects should release
underlying minifi objects within expected scope
[ https://issues.apache.org/jira/browse/MINIFICPP-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16256369#comment-16256369 ]
marco polo commented on MINIFICPP-308:
--------------------------------------
I added 0.3.0 to the version but I'll let you decide if it should if it should go into this release.
> Script objects should release underlying minifi objects within expected scope
> -----------------------------------------------------------------------------
>
> Key: MINIFICPP-308
> URL: https://issues.apache.org/jira/browse/MINIFICPP-308
> Project: NiFi MiNiFi C++
> Issue Type: Improvement
> Reporter: Andrew Christianson
> Assignee: Andrew Christianson
>
> ExecuteScript sessions are holding onto some underlying minifi objects, such as FlowFile instances, longer than we would like. This is due to the GC implementations of the scripting environments, for example:
> https://github.com/ThePhD/sol2/issues/129
> ExecuteScript should therefore offer proxy objects (FlowFile is already proxied by ScriptFlowFile) which release any resource-intensive minifi objects as soon as conditions are met where the script should not longer use them (after onTrigger of context/session, after transfer or remove for flow files).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)