You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Michael Moser (JIRA)" <ji...@apache.org> on 2016/10/07 19:01:20 UTC
[jira] [Updated] (NIFI-2611) UnpackContent cannot unpack any type
of flowfile
[ https://issues.apache.org/jira/browse/NIFI-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Moser updated NIFI-2611:
--------------------------------
Fix Version/s: (was: 0.8.0)
0.7.1
> 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
> Fix For: 1.0.0, 0.7.1
>
>
> 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)