Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created 06-20-2021 11:43 AM
Hi,
I have downloaded the latest version of Nifi 1.13.2. In one of my flows Im using an Execute script processor that utilizes python engine which I know it was working without problems in an older (version 1.11.4). I noticed when the processor executes for the first time it works then if you stop it and re run again it hangs and the flow files get stuck in the upstream queue. Initially I thought something in my script is causing the issue so I change it to something as simple as this
flowFile = session.get()
if flowFile != None:
# All processing code starts at this indent
session.transfer(flowFile, REL_SUCCESS)
Even with this simple script the processor hangs and the flow files remain in the queue. This is a major issue and its causing me not to upgrade. Not sure if you are aware of it and if if there is anything that can be done to mitigate. please advise.
Created 07-16-2021 11:33 AM
This appears to be fixed in the latest release 1.14.0. I will mark this as resolved. thanks
Created 06-23-2021 12:47 AM
I also get same issue. After I upgrade nifi 1.11.4 to 1.13.2, it shows
"
Failed to process session due to javax.script.ScriptException: Type Error: 'int' object is unsubscriptable in <script> at line number 51:
"
Created 07-16-2021 11:33 AM
This appears to be fixed in the latest release 1.14.0. I will mark this as resolved. thanks
Created 09-07-2021 04:30 AM
is it solved ?
Created 09-25-2021 03:57 PM
Its Solved after upgrading to 1.14.0
Created 09-08-2021 08:41 PM
I am having the same issue on 1.13.2 with execute script processor seeming to only work once. Did it work for you when you upgraded to 1.14.0?
Created 09-25-2021 03:55 PM
Its Solved in the latest version 1.14.0. I'm not sure if they addressed this issue in later releases of 1.13 version