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 W Moser (Jira)" <ji...@apache.org> on 2023/09/11 19:14:00 UTC

[jira] [Commented] (NIFI-12038) Create processor to package FlowFiles

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

Michael W Moser commented on NIFI-12038:
----------------------------------------

This was discussed a bit on Apache NiFi Slack channel

[https://apachenifi.slack.com/archives/C0L9S92JY/p1692115270146369]

 

> Create processor to package FlowFiles
> -------------------------------------
>
>                 Key: NIFI-12038
>                 URL: https://issues.apache.org/jira/browse/NIFI-12038
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Extensions
>            Reporter: Michael W Moser
>            Assignee: Michael W Moser
>            Priority: Minor
>
> h4. Design Goals
> Provide a simple way to package FlowFile attributes and content into FlowFileV3 format that can be exported from NiFi and reimported later. MergeContent can do this, but it is not intuitive that it has this capability, and it can be complicated to setup perfectly.
> h4. Use Cases
>  * Package FlowFile for external (off-NiFi) storage, for later ingest back into NiFi using an ingress processor followed by UnpackContent
>  * Package FlowFile for NiFi-to-NiFi transfer when a direct connection is not possible, or another transfer mechanism is required
>  * Package FlowFile then InvokeHTTP directly to another NiFi running ListenHTTP, which can natively unpack FlowFileV3 format
> h4. Other Ideas
>  * Offer best-effort, no guarantee N FlowFiles to 1 bundling
>  * Create new FlowFile serialization format to support interoperability with non-NiFi services, such as core operating system tools



--
This message was sent by Atlassian Jira
(v8.20.10#820010)