Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.7.0
-
None
-
Important
Description
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
Attachments
Issue Links
- links to