You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Matthieu RÉ (Jira)" <ji...@apache.org> on 2022/07/15 14:58:00 UTC

[jira] (NIFI-10236) ByteArrayContentRepository in core framework

    [ https://issues.apache.org/jira/browse/NIFI-10236 ]


    Matthieu RÉ deleted comment on NIFI-10236:
    ------------------------------------

was (Author: mathemare):
Oh, it was not your point, I'm sorry! About the possibility to use the stateless engine, our main blocking point among others was that we need in our current use-case to operate our Flows directly through NiFi UI (investigating transformation, potential bugs in production without having the need to commit and apply through NiFi Registry), from my understanding it is not the spirit of the Stateless implementation.

> 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)