[
https://issues.apache.org/jira/browse/NIFI-15331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18044529#comment-18044529
]
ASF subversion and git services commented on NIFI-15331:
--------------------------------------------------------
Commit c7a16c4cf6efa3116eda57b8d02ebefaa15b9c5a in nifi's branch
refs/heads/NIFI-15318-2 from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=c7a16c4cf6e ]
NIFI-15331 Fixed Script Engine property name migration from 2.7.0 (#10634)
Signed-off-by: Daniel Stieglitz <[email protected]>
> 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
> Fix For: 2.8.0, 2.7.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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)
