[jira] [Assigned] (NIFI-15331) ExecuteScript migration of properties not working as expected.

["David Handermann (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-15331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Handermann reassigned NIFI-15331:
---------------------------------------

    Assignee: David Handermann

> ExecuteScript migration of properties not working as expected.
> --------------------------------------------------------------
>
>                 Key: NIFI-15331
>                 URL: https://issues.apache.org/jira/browse/NIFI-15331
>             Project: Apache NiFi
>          Issue Type: Bug
>            Reporter: Daniel Stieglitz
>            Assignee: David Handermann
>            Priority: Major
>
> The work in NIFI-15317 was meant to correct the bug introduced with NIFI-15108 with the scripting components. While the fix worked for components
>  - InvokeScriptedProcessor
>  - ScriptedReportingTask
>  - ScriptedLookupService
>  - ScriptedReader
>  - ScriptedRecordSetWriter
>  - ScriptedRecordSink
>  - SimpleScriptedLookupService
> it did not work for the ExecuteScript processor as can seen below.
> For 2.5.0 I have an ExecuteScript processor whose properties are:
> {code:java}
> "properties": {
> "Script File": "someFile",
> "Script Engine": "Groovy"
> }{code}
> When upgrading to 2.7.0 the properties are
> {code:java}
> "properties": {
> "Script File": "someFile",
> "Script Language": "Clojure",
> "Script Engine": "Groovy"
> }{code}
> After upgrading to 2.7.1 the properties are
> {code:java}
> "properties": {
> "Script File": "someFile",
> "Script Engine": "Clojure"
> }{code}
> For 2.7.1 the {{"Script Engine"}}  property value should be {{"Groovy"}}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)