[ https://issues.apache.org/jira/browse/MINIFI-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16014411#comment-16014411 ]
ASF GitHub Bot commented on MINIFI-37: -------------------------------------- Github user apiri commented on a diff in the pull request: https://github.com/apache/nifi-minifi-cpp/pull/98#discussion_r117001436 --- Diff: libminifi/include/core/Repository.h --- @@ -47,14 +47,21 @@ namespace nifi { namespace minifi { namespace core { +#define REPOSITORY_DIRECTORY "./repo" --- End diff -- Should we expose these out to our properties file as well? Can create a ticket to do so at a later juncture. > Native Volatile Content Repository implementation > ------------------------------------------------- > > Key: MINIFI-37 > URL: https://issues.apache.org/jira/browse/MINIFI-37 > Project: Apache NiFi MiNiFi > Issue Type: Task > Components: C++, Core Framework > Reporter: Aldrin Piri > Assignee: marco polo > Priority: Minor > Labels: native > > Given the constrained environments in which MiNiFi could operate, it would be > beneficial to provide a content repository that is strictly in memory for > those environments where disk storage may be limited or non-existent. > This implementation should consider configuration options around its > footprint such as number of entries held and/or sheer capacity. -- This message was sent by Atlassian JIRA (v6.3.15#6346)