Ok, for those whom it may concern:

the issue is not in "reading" the file, but merely in the fact that the
file is "stuck" in the processor. Adding "REL_SUCCESS << flowFile" as last
line and things are working.

Am Fr., 10. Jan. 2025 um 16:26 Uhr schrieb Bjoern Wuest <
bjoern.wu...@gmx.net>:

> Hi,
>
> I am on nifi 2.1.0 . When executing (even as only line) the command "def
> flowFile = session.get()", I receive the following error message:
>
> ExecuteScript[id=5065aacc-0194-1000-35e2-a707c1752fa8] Processing failed:
> org.apache.nifi.processor.exception.ProcessException:
> org.apache.nifi.processor.exception.FlowFileHandlingException:
> StandardFlowFileRecord[uuid=ee4f62cf-cec1-4c0e-9cca-03f8e3e877f1,claim=StandardContentClaim
> [resourceClaim=StandardResourceClaim[id=1736514978089-7, container=default,
> section=7], offset=3318,
> length=348084],offset=0,name=30d35e94-0d3e-4e18-a819-5bfc21b6a012,size=348084]
> transfer relationship not specified. This FlowFile was not created in this
> session and was not transferred to any Relationship via
> ProcessSession.transfer()
> - Caused by:
> org.apache.nifi.processor.exception.FlowFileHandlingException:
> StandardFlowFileRecord[uuid=ee4f62cf-cec1-4c0e-9cca-03f8e3e877f1,claim=StandardContentClaim
> [resourceClaim=StandardResourceClaim[id=1736514978089-7, container=default,
> section=7], offset=3318,
> length=348084],offset=0,name=30d35e94-0d3e-4e18-a819-5bfc21b6a012,size=348084]
> transfer relationship not specified. This FlowFile was not created in this
> session and was not transferred to any Relationship via
> ProcessSession.transfer()
>
> I can see that the file with ID ee4f... is in the queue to the
> ExecuteGroovyScript processor. Config of this processor is:
> Script file: empty
> Script body: def flowFile = session.get()
> Failure strategy: rollback
> Additional classpath: empty
>
> Any hint why the flow file is not handed over to the script processor? And
> any idea while the get() fails since it could as well also return a "null"?
>
> Thank you
>   Bjoern
>
>

Reply via email to