This does not impact running of tests. I stumbled into these errors when debugging the Nifi flow while investigating ASCVD failures.
The error message:
InvokeScriptedProcessor[id=bd38dc04-e99c-395e-a816-0b8da5df640d] Failed to properly initialize Processor. If still scheduled to run, NiFi will attempt to initialize and run the Processor again after the 'Administrative Yield Duration' has elapsed. Failure is due to org.apache.nifi.processor.exception.ProcessException: Error creating ScriptRunner: org.apache.nifi.processor.exception.ProcessException: Error creating ScriptRunner
The process id noted in the message is for the "Break up error message if too large" processor.
David says this is a script in the "MM" flow that we base our nifi one.
("MM" refers to Mike Payne and Mike Britt)
This does not impact running of tests. I stumbled into these errors when debugging the Nifi flow while investigating ASCVD failures.
The error message:
InvokeScriptedProcessor[id=bd38dc04-e99c-395e-a816-0b8da5df640d] Failed to properly initialize Processor. If still scheduled to run, NiFi will attempt to initialize and run the Processor again after the 'Administrative Yield Duration' has elapsed. Failure is due to org.apache.nifi.processor.exception.ProcessException: Error creating ScriptRunner: org.apache.nifi.processor.exception.ProcessException: Error creating ScriptRunner
The process id noted in the message is for the "Break up error message if too large" processor.
David says this is a script in the "MM" flow that we base our nifi one.
("MM" refers to Mike Payne and Mike Britt)