[
https://issues.apache.org/jira/browse/NIFI-8950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-8950:
-----------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Allow Stateless NiFi to use a file system backed Content Repository
> -------------------------------------------------------------------
>
> Key: NIFI-8950
> URL: https://issues.apache.org/jira/browse/NIFI-8950
> Project: Apache NiFi
> Issue Type: New Feature
> Components: NiFi Stateless
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.15.0
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> Stateless NiFi is capable of storing all FlowFile content on Java Heap. This
> is often what we want to do, as often times this is used for small 'message'
> types of flows. However, there are times when we do not want to do this. For
> example, consider a scenario in which we want to download a file from S3 and
> push it to some other S3 bucket. If that file is several GB, we may not have
> the resources to store the entire contents in Java heap.
> Instead, we may want to store the data in 'scratch space'. This change would
> *NOT* result in data being persistent across restarts of the application - or
> even across successive triggerings of the dataflow. I.e., this is not
> intended to provide stateful, persistent storage of the data, but rather to
> allow for larger FlowFiles than what can fit in memory to still be operated
> on by Stateless NiFi
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
