markap14 opened a new pull request, #11676: URL: https://github.com/apache/nifi/pull/11676
## Summary [NIFI-16271](https://issues.apache.org/jira/browse/NIFI-16271) Allows a Stateless Process Group to buffer FlowFile content in memory up to a data-size cap and/or a heap-percentage cap, then spill to the Content Repository. Content that leaves the group is written to on-disk claims before the FlowFile Repository is updated. - Default is `0%` heap and an unset data size, which uses no in-memory content. - Zero means zero; unset means not configured. If only one limit is set, that limit is used. If both are set, the smaller of the two is used (for example, 80% up to 4 GB). - The budget applies to the Stateless group as a whole, including Concurrent Tasks. - The in-memory limits cannot be changed while the Stateless group is running. **Draft:** this PR depends on `nifi-api` `2.12.0-SNAPSHOT` from [apache/nifi-api#108](https://github.com/apache/nifi-api/pull/108). It cannot merge until that API change is released. ## Test plan - [x] Unit tests for spillable in-memory content, Process Group limit resolution (size-only, percent-only, min of both, unset/zero), and related Stateless flow-task behavior - [x] System test `StatelessInMemoryContentIT` for under-budget in-memory content, spill-over, and rejecting limit changes while running - [ ] `./mvnw clean install -P contrib-check` (JDK 21 / JDK 25) after the API snapshot is available in CI - [ ] UI: Stateless Process Group dialog shows both limits and disables them while the group is running -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
