[ https://issues.apache.org/jira/browse/MINIFI-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16014408#comment-16014408 ]
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_r116998366 --- Diff: libminifi/src/core/RepositoryFactory.cpp --- @@ -48,9 +50,15 @@ std::shared_ptr<core::Repository> createRepository( try { std::shared_ptr<core::Repository> return_obj = nullptr; if (class_name_lc == "flowfilerepository") { + std::cout << "creating flow" << std::endl; --- End diff -- should it be logged instead? > 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)