@Matt / @Peter, I have faced problems if incorrect input is passed to ExecuteScript processor and it would need some manual intervention to cleanup the 'buggy' flowFile. The job fails on Production and keeps retrying if we dont route the incorrect flowFile to FAILURE. I generally use try-catch strategy to move the incorrect flowFiles to FAILURE path and add the exception as a attribute that finally gets logged in nifi-app.log.
Modified example below using Peter's if construct-
if (flowFile!=None):
try:
reader = PyStreamCallback()
flowFile = session.write(flowFile,reader)
flowFile = session.putAttribute(flowFile,'ThisIsAnAttributeName',reader.thing())
session.transfer(flowFile, REL_SUCCESS)
except Exception as e:
attrMap = {}
attrMap["Script.Exception"] = e
session.putAllAttribute(flowFile,attrMap)
session.transfer(flowFile, REL_FAILURE)
... View more
