[
https://issues.apache.org/jira/browse/NIFI-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430965#comment-15430965
]
ASF GitHub Bot commented on NIFI-2611:
--------------------------------------
Github user mosermw commented on a diff in the pull request:
https://github.com/apache/nifi/pull/905#discussion_r75697030
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/test/java/org/apache/nifi/processors/standard/TestUnpackContent.java
---
@@ -199,11 +199,12 @@ public void testFlowFileStreamV3() throws IOException
{
final TestRunner runner = TestRunners.newTestRunner(new
UnpackContent());
runner.setProperty(UnpackContent.PACKAGING_FORMAT,
UnpackContent.PackageFormat.FLOWFILE_STREAM_FORMAT_V3.toString());
runner.enqueue(dataPath.resolve("data.flowfilev3"));
+ runner.enqueue(dataPath.resolve("data.flowfilev3"));
- runner.run();
+ runner.run(2);
- runner.assertTransferCount(UnpackContent.REL_SUCCESS, 2);
- runner.assertTransferCount(UnpackContent.REL_ORIGINAL, 1);
+ runner.assertTransferCount(UnpackContent.REL_SUCCESS, 4);
+ runner.assertTransferCount(UnpackContent.REL_ORIGINAL, 2);
--- End diff --
I would like to see this pattern (send 2 flowfiles) in other unit tests,
too. Can we add this to testTar(), testTarWithFilter(), testZip(),
testZipWithFilter(), and testFlowFileStreamV2()?
> 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
> Assignee: 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)