[
https://issues.apache.org/jira/browse/NIFI-12304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17888779#comment-17888779
]
ASF subversion and git services commented on NIFI-12304:
--------------------------------------------------------
Commit 1bfdf3c107c958ca48ef4dc4e08feee5a5b786cb in nifi's branch
refs/heads/main from Michael W Moser
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=1bfdf3c107 ]
NIFI-12304 Added FlowFileV3 Unpacking to ListenHTTP as a documented UseCase
(#9369)
Signed-off-by: David Handermann <[email protected]>
> Document ListenHTTP content unpack behaviour
> --------------------------------------------
>
> Key: NIFI-12304
> URL: https://issues.apache.org/jira/browse/NIFI-12304
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Documentation & Website
> Affects Versions: 1.23.2
> Reporter: Peter Kimberley
> Assignee: Michael W Moser
> Priority: Minor
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {{ListenHTTP}} depending on the MIME type, will unpack received content
> automatically. For example, if using {{InvokeHTTP}} with a flowfile packed in
> {{FlowFile Stream v3}} format, with the {{mime.type}} attribute set to
> {{application/flowfile-v3}}.
> When {{ListenHTTP}} receives the payload, it will interpret the MIME type and
> if it matches a well-known value (i.e. {{application/flowfile-v3}}), the
> content will automatically be unpacked by this processor.
> While that's a handy feature, it is potentially confusing as this inline
> unpacking behaviour isn't documented, and a reasonable expectation is that
> one needs to {{UnpackContent}} separately in a subsequent processor.
> Recommend adding some use case documentation to {{ListenHTTP}}, to avoid
> confusion.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
