[ https://issues.apache.org/jira/browse/NIFI-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431301#comment-15431301 ]
ASF GitHub Bot commented on NIFI-2611: -------------------------------------- Github user mosermw commented on the issue: https://github.com/apache/nifi/pull/905 @gresockj this PR looks great, it passes contrib-check and I ran a bunch of configurations (MergeContent -> UnpackContent) based on your screenshot in the JIRA ticket. +1 will merge shortly. Do you mind if I squash your commits when I merge to 0.x to make it easier to merge into master? > 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)