[
https://issues.apache.org/jira/browse/NIFI-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429407#comment-15429407
]
Joseph Gresock commented on NIFI-2611:
--------------------------------------
As for the other bug (FFv2 and 3), I think I tracked it down to the fact that
the Unpacker is cached, but FlowFileUnpackagerV2 and V3's hasMoreData() method
rely on the haveReadSomething member variable being false for the initial read.
After the first flow file is processed, haveReadSomething is now true, and
subsequent flow files fail.
This can be demonstrated in the TestUnpackContent.testFlowFileStreamV3() method
by changing lines 202-204 to:
runner.enqueue(dataPath.resolve("data.flowfilev3"));
runner.enqueue(dataPath.resolve("data.flowfilev3"));
runner.run(2);
This demonstrates that there is one failure flow file.
I would resolve this myself, but I'm a little hesitant to mess with how the
Unpackers are cached since this is such a widely used processor.
> UnpackContent cannot unpack any type of flowfile
> ------------------------------------------------
>
> Key: NIFI-2611
> URL: https://issues.apache.org/jira/browse/NIFI-2611
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 0.7.0
> Reporter: Joseph Gresock
>
> Two possibly separate problems:
> *Flowfile-stream-v2 and v3*
> This may be a problem with either MergeContent's production of
> flowfile-stream v2 and v3, or with UnpackContent's inability to unpack them,
> not sure which. Here is a screen shot with how to reproduce it:
> https://ibin.co/2sCwqbFbAs3a.png
> Essentially, when you pack a flow file as flowfile-stream v2 or v3, a
> subsequent UnpackContent set to the respective type fails with the error
> "Cannot unpack {} because it does not appear to have any entries".
> *Flowfile-tar-v1*
> When selecting flowfile-tar-v1 from UnpackContent, you immediately get
> @OnScheduled error failure as soon as you start the processor, which prevents
> it from processing any incoming flow files. Here is a screenshot:
> https://ibin.co/2sCxI4iDm88t.png
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
