You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "David Handermann (Jira)" <ji...@apache.org> on 2023/06/02 09:41:00 UTC
[jira] [Updated] (NIFI-11630) Deprecate ECMAScript Script Engine
[ https://issues.apache.org/jira/browse/NIFI-11630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Handermann updated NIFI-11630:
------------------------------------
Summary: Deprecate ECMAScript Script Engine (was: Deprecate ECMAScript and python Script Engines)
> Deprecate ECMAScript Script Engine
> ----------------------------------
>
> Key: NIFI-11630
> URL: https://issues.apache.org/jira/browse/NIFI-11630
> Project: Apache NiFi
> Issue Type: Task
> Components: Extensions
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Major
> Fix For: 1.latest
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The {{ECMAScript}} and {{python}} Script Engines for multiple scripted Processors and Controller Services should be deprecated for removal in NiFi 2.0.
> The {{ECMAScript}} engine supports JavaScript-compatible scripted components. The Nashorn engine was deprecated in Java 11 as described in [JEP 335|https://openjdk.org/jeps/335] and is no longer available in Java 17. Alternative JavaScript engines could be considered separately, but {{ECMAScript}} should be deprecated for removal.
> The {{python}} engine supports Python-compatible scripted components using [Jython|https://www.jython.org/]. Experimental framework support for native Python Processors is available in the current main branch, which will provide a clear alternative to Jython-based scripting.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)