[ https://issues.apache.org/jira/browse/NIFI-12038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17771070#comment-17771070 ]
ASF subversion and git services commented on NIFI-12038: -------------------------------------------------------- Commit 4c5ea5f4da58ac26ad7d450c194834db72a8ae1d in nifi's branch refs/heads/support/nifi-1.x from Michael W Moser [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=4c5ea5f4da ] NIFI-12038 This closes #7760. introduce PackageFlowFile processor Signed-off-by: Joseph Witt <joew...@apache.org> > 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 > Fix For: 2.0.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > 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)