[
https://issues.apache.org/jira/browse/NIFI-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431405#comment-15431405
]
ASF subversion and git services commented on NIFI-2611:
-------------------------------------------------------
Commit fd7462b6532728373071314d44171be92762dc43 in nifi's branch refs/heads/0.x
from Joe Gresock
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=fd7462b ]
NIFI-2611: Fixing bugs in UnpackContent with flow file unpackers
Signed-off-by: Mike Moser <[email protected]>
This closes #905
> 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)
