[
https://issues.apache.org/jira/browse/NIFI-10236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17567267#comment-17567267
]
Matthieu RÉ commented on NIFI-10236:
------------------------------------
Hello David,
Sorry for that!
Yes I first tried to use the ByteArrayContentRepository from the nifi-stateless
framework, but there were two limits (in my non-expert opinion) for it to be
directly set in the core framework :
* the current implementation does not set limits to the max size it should
take in memory, and does not provide the ability to get the size the contents
occupy
* the current StandardProcessSession tries in its current implementation to
use a StandardContentClaim to be stored in a Cache
([StandardContentClaimWriteCache|https://github.com/apache/nifi/blob/main/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/repository/claim/StandardContentClaimWriteCache.java#L87]),
and the StandardContentClaim is not implemented by the current
ByteArrayContentRepository
The proposed implementation tries to solve these two requirements... but if I
can have misunderstood something about the two points or their need
> ByteArrayContentRepository in core framework
> --------------------------------------------
>
> Key: NIFI-10236
> URL: https://issues.apache.org/jira/browse/NIFI-10236
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Core Framework
> Affects Versions: 1.17.0
> Reporter: Matthieu RÉ
> Assignee: Matthieu RÉ
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> As discussed in NIFI-8760 and by mail, the use case of using an in-memory
> based implementation of the ContentRepository is not completed after 1.17.0
> and the removal of the old VolatileContentRepository (NIFI-9823) when the
> ExecuteStateless is not a solution.
> As proposed by mail, the ByteArrayContentRepository could be duplicated from
> the nifi-stateless framework to the core one, but maybe with more
> functionalities, for instance the follow-up of the space taken in memory, and
> the limitation of its total usage.
> Don't hesitate to comment, add or discuss requirements or the implementation
> I will propose.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
