Uploaded image for project: 'Apache NiFi'
  1. Apache NiFi
  2. NIFI-12304

Document ListenHTTP content unpack behaviour

Details

    • Improvement
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • None
    • 2.0.0
    • None

    Description

      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.

      Attachments

        Issue Links

          Activity

            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 <exceptionfactory@apache.org>

            jira-bot ASF subversion and git services added a comment - 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 <exceptionfactory@apache.org>

            People

              mosermw Michael W Moser
              p-kimberley Peter Kimberley
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 20m
                  20m