You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Joseph Gresock (JIRA)" <ji...@apache.org> on 2016/08/20 15:03:20 UTC

[jira] [Comment Edited] (NIFI-2611) UnpackContent cannot unpack any type of flowfile

    [ https://issues.apache.org/jira/browse/NIFI-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429398#comment-15429398 ] 

Joseph Gresock edited comment on NIFI-2611 at 8/20/16 3:02 PM:
---------------------------------------------------------------

This is the stack trace for the FF-v1 error.  It appears that the PackageFormat is possibly null:

Caused by: java.lang.NullPointerException: null
        at org.apache.nifi.processors.standard.UnpackContent.initUnpacker(UnpackContent.java:199) ~[na:na]
        at org.apache.nifi.processors.standard.UnpackContent.onScheduled(UnpackContent.java:194) ~[na:na]
        ... 14 common frames omitted

Turns out this is because of line UnpackContent:539, whose case statement checks for "flowfile-stream-v1", but the actual property is set to "flowfile-tar-v1".  

This should be a 1-line fix, but I figured it might as well be fixed at the same time as the other problem, which is a little more complex (see comment below).


was (Author: jgresock):
This is the stack trace for the FF-v1 error.  It appears that the PackageFormat is possibly null:

Caused by: java.lang.NullPointerException: null
        at org.apache.nifi.processors.standard.UnpackContent.initUnpacker(UnpackContent.java:199) ~[na:na]
        at org.apache.nifi.processors.standard.UnpackContent.onScheduled(UnpackContent.java:194) ~[na:na]
        ... 14 common frames omitted

I am using OpenJDK8 u91 on CentOs 6.8 when I get this exception.

> 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)