[
https://issues.apache.org/jira/browse/NIFI-10236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17567381#comment-17567381
]
Mark Payne commented on NIFI-10236:
-----------------------------------
Yeah I think it makes more sense to move the ByteArrayContentRepository from
the nifi-stateless-engine to the nifi-framework-components module. We don't
want to have two implementations to maintain.
The repository can definitely be updated to take an optional max size.
With respect to the StandardContentClaim and caching: I don't think it makes
sense to introduce a new CachableContentClaim interface at this time. The
setLength() is needed by StandrdContentClaimWriteCache. However, the claim that
it is working with is always one that is returned by
StandardContentClaimWriteCache.getContentClaim(). So it would make more sense
to leave the Content Repository returning whatever type of Content Claim it
wants. And then update the StandardContentClaimWriteCache's getContentClaim()
method to just wrap the ContentClaim in its own internal implementation that
allows the Length to be set.
> 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)
