[NIFI-9823] Remove VolatileContentRepository

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.17.0
• Component/s: Core Framework
• Assignee: David Handermann
• Reporter: David Handermann
• Created: 22/Mar/22 18:36
• Updated: 29/Mar/22 11:16
• Resolved: 29/Mar/22 11:16

Description

The VolatileContentRepository implementation of the Content Repository interface supports storing FlowFile content claims in heap memory without writing to a file system. Although this capability has potential uses, the implementation is not optimal, and the repository itself has been broken for several releases. Several framework updates to content claim processing result in expected behavior when using the VolatileContentRepository, leading to problems that can be difficult to troubleshoot. For these reasons, the current VolatileContentRepository and associated documentation should be removed from future releases.

Future efforts to support a similar capabilities may build on NiFi Stateless functionality, and those efforts can be addressed in separate issues.

Issue Links

• supercedes: NIFI-7388 Bug reports about VolatileContentRepository and VolatileFlowFileRepository
• supercedes: NIFI-8760 VolatileContentRepository fails to retrieve content from claims with several processors
• supercedes: NIFI-1287 Inefficient thread utilization in VolatileContentRepository
• links to: GitHub Pull Request #5889